Structured Model
Uploaded by
ScribdTranslationsStructured Model
Uploaded by
ScribdTranslations2.3 Structured Model.
In the structured model, the nine activities and the three are briefly examined.
terminators that compose it, as shown in figure 2.3.1. The terminators
they are the users, the administrators, and the operations staff. Which are dealt with
of individuals or groups that provide input to the project team, and are the
final beneficiaries of the system.
Figure 2.3: Structured Model
Activity 1: The survey
This activity is also known as the feasibility study or as the study
business initiation. It starts when the user requests that one or more parts of their
systems are automated. The main objectives of the survey are:
Identify the responsible users and create an initial 'activity field'
of the system.
Identify the current deficiencies in the user environment.
Establish goals and objectives for a new system.
Determine if it is feasible to automate the system and, if so, suggest scenarios.
acceptable.
Prepare the outline that will be used to guide the rest of the project.
In general, the survey takes only 5 to 10 percent of time and resources.
the entire project, and for small and simple projects it might not even be a
formal activity. Despite all the above, it is an important activity because
the management could decide to cancel the project if it does not seem attractive from the
cost-benefit perspective.
Activity 2: Systems analysis
The main purpose of the analysis activity is to transform its two inputs - or
inputs or factors - main, the user's policies and the project scheme, in
a structured specification. This involves modeling the user's environment with
data flow diagrams, entity-relationship diagrams, transition diagrams
state, etc.
The step-by-step process of systems analysis involves the development of a model
environmental and the development of a behavioral model, which combine to
to form the essential model that represents a formal description of what the new
the system must do, regardless of the nature of the technology used
to meet the requirements.
At the end of the analysis activity, a set must also be prepared.
more accurate and detailed budgets and cost-benefit calculations.
Activity 3: The design
The design activity is dedicated to assigning portions of the specification (model
essential) to suitable processors (machines or humans) and to appropriate tasks (or
tasks, partitions, etc.) within each processor. Within each task, the activity of
design is dedicated to the creation of an appropriate hierarchy of program modules and
interfaces between them to implement the specification created in activity 2. In addition,
it deals with the transformation of entity-relationship data models into a design of
database.
Activity 4: Implementation
This activity includes coding and integrating modules into a skeleton.
progressively more complex of the final system. That is why activity 4 includes both
structured programming as top-down implementation.
Activity 5: Generation of acceptance tests
The structured specification must contain all the information needed to define
a system that is acceptable from the user's point of view. For that reason, once
Once the specification is generated, you can begin the activity of producing a set of
acceptance test cases from the structured specification.
Activity 6: Quality Assurance
The quality assurance is also known as the final test or the test of
acceptance. This activity requires as inputs the acceptance test data
generated in activity 5 and the integrated system produced in activity 4.
Activity 7: Description of the procedure
This activity involves the generation of a formal description of the parts of the system.
that will be done manually, just like the description of how they will interact
users with the automated part of the new system. The result of activity 7 is
a user manual.
Activity 8: Database Conversion
In some projects, the database conversion involved more work than the
development of computer programs for the new system. In other cases, it could
there was no database to convert. In the general case, this activity
requires as input the user's current database, as well as the specification
of the design produced through activity 3.
Activity 9: Installation
In this activity, your inputs are the user manual produced in activity 7,
converted database created with activity 8 and the accepted system produced
for activity 6. In some cases, the installation could simply mean a
change from night to morning to the new system; in other cases, the installation could
it's a gradual process, in which one group after another of users receive manuals
your training and started using the new system.
