|
System elements |
|||
|
1.
Data |
Logical Data Model (LDM) |
The class diagram |
A. The class diagram B. Databases |
|
2.
Events |
Entity Life History (ELH) |
The Behaviour (interaction) diagrams |
The Behaviour (interaction) diagrams |
|
3.
Processes |
Data Flow Diagram (DFD) |
The activity diagram |
The activity diagram |
|
4.
Interfaces |
Dialogue Design |
Modelled in class and component diagrams. |
A, User screen sketches/prototypes. B. Internal interfaces: classes and
components. |
|
5.
Resources |
Requirements Catalogue (RC). |
Modelled by using the stereotype feature. |
Project manager plans and schedules process
resources. |
|
6.
Quality |
Requirements Catalogue (RC). |
A. In analysis
explorative prototypes. B. In design experimental prototypes |
A. Inception and
elaboration phases: explorative prototypes. B. Tests: Integration, configuration,
negative and stress. |
|
7.
Business
issues |
A. Data Flow Diagrams
(DFD). B. Entity Life History (ELH). |
Activity diagrams describe and model
business process. |
Developing business model that defines
business processes. |
|
8.
Identify the
problem or problem objectives |
The strategic planning defines the problem
that needs to be solved. |
The strategic planning defines the problem
that needs to be solved. |
The strategic planning defines the problem
that needs to be solved. |
|
9.
User
involve-ment |
A. Gathering
information about system. B. Reviewing products of each stage. |
A. Gathering info-
rmation about system in use case models, CRC and tech. dictionary. B. Review/check prototypes. |
A. Gathering
info-rmation about system in use cases, business or domain models,
suppl. requirements. B. Check/validate arte-facts of
iteration//phases. |
|
10.
Organi-sational
structure, goals and policies |
Strategic planning looks at organi-sational
structure giving Project Initial
Document. |
Activity diagram models organisational
structure and integration. |
Documented in the business model and
supplementary requirements. |
|
11.
Employee job
satisfaction |
User may choose Business System Option
(BSO) that defining impact on users and training. |
Allowing employees to choose suitable way
to perform assigned job. |
Project feasibility, risk management, team
structure, project schedule, project under-standability and sense of
accomplishment |
|
12.
Different
point of views |
Different views of the system are
documented in Requirements Catalogue. |
Analyst considers different views of system
and resolves contradictions. |
Different views are integrated to reach
best answer. |
|
13.
Employee
values |
Not Supported. |
Not Supported. |
Not supported |
|
14.
System
accepta-bility and usability |
A. User involve-ment in
developing system. B. Use prototype. C. Study of system impact on staff. |
Involvement of users in experi-mental
prototypes to verify usability/accepta-bility of system. |
A. Involving user in
developing system. B. Performing acceptance test. C. Providing users with doc/help line. |
|
|
|
|
|
|
|
|
|
|
Extracted from “Evaluation of Systems Analysis Methodologies
in a Workflow Context “
Fahad Al-Humaidan B.
Nick Rossiter
Computing Science Computing and Mathematics
Newcastle University Northumbria
University
Newcastle upon Tyne Newcastle upon Tyne
NE1 7RU, UK NE1 8ST, UK
Tele:
++44 191 227 4662
nick.rossiter@unn.ac.uk