טכניון מכון טכנולוגי לישראל
הטכניון מכון טכנולוגי לישראל - בית הספר ללימודי מוסמכים  
M.Sc Thesis
M.Sc StudentSalus Aylon
SubjectA Specification Document for an Internet Site using the
MethodA(TM) Methodology with UML and A Comparison
to A Information System that was
Formulated without Specificat
DepartmentDepartment of Quality Assurance and Reliability
Supervisor Dr. Amir Tomer


Abstract

The paper discusses procedures of quality assurance in computerized information systems, and is composed of two parts:

  1. A system specification document for an information system, arranged according to MethodaA ™ methodology - a framework for the development and maintenance of computerized information systems, combined with UML (Unified Modeling Language) - a language for the analysis and design of information systems.
  2. A comparative study between the information system that was implemented according to the specification document and an existing similar information system that was built without an orderly procedure.

The study compares between the different users of information systems, who are divided into three sample groups: students, academic staff and academic secretaries.              

All three groups evaluated the two information systems based on a set of quality metrics.

There are two main findings to the paper:

  1. A specification document can be applied in accordance with MethodaA ™ methodology combined with UML.
  2. The information system that was implemented according to the specification document is of better quality than the existing information system, according to the quality metrics. The various groups differ in their evaluations.

These findings can lead to the conclusion that building a system on the basis of an orderly procedure in general, and on the basis of a specification document combined with UML in particular, is expected to yield a system of higher quality. An additional conclusion is that it is better to identify all the system users and analyze their requirements during the specification phase rather than focus only on the main user. This leads to a system with a higher level of correctness and with fewer changes to the system in late life cycle phases, which are very costly.