8/4/2015 System Analysis

and Design
Information System form
Eastern State University

Ramodi Dissanayake
BCAS KANDY CAMPUS
HND 31
SEMESTER 2
 System Analysis and Design

Contents
Acknowledgement......................................................................................................................................2
Figures and Tables......................................................................................................................................3
Introduction................................................................................................................................................4
Task 1.1 (P1.1).............................................................................................................................................7
Evaluate different system Development Lifecycle models........................................................................7
Why we need SDLC.................................................................................................................................7
Waterfall Model......................................................................................................................................7
RAD Model............................................................................................................................................10
Prototyping Model................................................................................................................................12
Spiral Model..........................................................................................................................................13
Iterative Model.....................................................................................................................................15
Agile Model...........................................................................................................................................16
Dynamic system Development Method...............................................................................................18
Task 1.2 (P1.2, M3.3)................................................................................................................................20
Create a document for the lifecycle stages and do the presentation......................................................20
Task 1.3 (M1.1).........................................................................................................................................28
Select the one of SDLC Model suited to the scenario and justify the selection......................................28
Task 1.4 (M2.3).........................................................................................................................................30
Discuss the application of the DSMD to the given scenario.....................................................................30
What is the DSMD.................................................................................................................................30
Task 1.5 (D1.1)..........................................................................................................................................34
Different type of fact finding techniques.................................................................................................34
Conclusion.................................................................................................................................................39
Reference..................................................................................................................................................40

pg. 1
 System Analysis and Design

Acknowledgement
Frist of all I would like to thank my parent who helped me lot and I want to thanks our System
Analysis and Design lecturer Mr. Roshan who gave us lot of guides and advice to do this
assignment. In addition, I really thank all the people who helped me lot.

Then I would like to thank my dear friends for all the support they have given me in completing
this assignment.

And then I would like to express my appreciation to the BRITSH COLLEAGE OF APPLIED
STUDIES for all the support and providing us with qualified lecturers, and the computer labs
which had been so much of use in the process of this assignment.

Thank you,

Ramodi Dissanayake.

pg. 2
 System Analysis and Design

Figures and Tables

Figure 1 (waterfall Model)...........................................................................................................................9
Table 1 (Advantages and Disadvantages of waterfall model)....................................................................10
Figure 2 (RAD Model)................................................................................................................................11
Table 2 (Advantages and Disadvantages RAD Model)...............................................................................11
Figure 3 (Prototyping Model)....................................................................................................................12
Table 3 (Advantages and Disadvantages of Prototyping)..........................................................................13
Figure 4 (Spiral Model)..............................................................................................................................14
Table 4 (Advantages and Disadvantages of spiral Model).........................................................................14
Figure 5 (Iterative Model)..........................................................................................................................15
Table 5 (Advantages and Disadvantages of Iterative Model)....................................................................15
Figure 6 (Agile Model)...............................................................................................................................16
Table 6 (Advantages and Disadvantages of Agile Model)..........................................................................17
Figure 7 (DSDM Model).............................................................................................................................19
Figure 8 (Task presentation)......................................................................................................................23
Figure 9 (Task presentation)......................................................................................................................23
Figure 10 (Task presentation)....................................................................................................................24
Figure 11(Task presentation).....................................................................................................................24
Figure 12 (Task presentation)....................................................................................................................25
Figure 13 (Task presentation)....................................................................................................................25
Figure 14 (Task presentation)....................................................................................................................26
Figure 15 (Task presentation)....................................................................................................................26
Figure 17 (Task presentation)....................................................................................................................27
Figure 18 (Task presentation)....................................................................................................................27
Figure 19 (Task presentation)....................................................................................................................27
Figure 20 (DSDM Diagram)........................................................................................................................31

pg. 3
 System Analysis and Design

Introduction
Purpose of this assignment is the system life cycle provides a comprehensive framework for
initially capturing data and information through a feasibility study and the use of recognized fact
finding techniques. The systems development life cycle (SDLC) is a conceptual model used in
project management that describes the stages involved in an information system development
project, from an initial feasibility study through maintenance of the completed application. In
here customer describes the vision for the system to the developer. This idea is transformed into
sketches and drawings that are shown to the customer and refined until the customer agrees.
Develop the blue print. Build the system.
SDLC models program development is faster when programmers come together to create the
workflow instead of going through a lot of user inputs and requirements. Developers can work
on the problem and create a solution based on the need. With an SDLC Model, developers can
take clear idea on what should be or shouldn’t be built. With an SDLC Model, programs can
have a documentation of development, structure and even coding. Aside from longer lifespan of
an SDLC modeled program, every created program could serve be used in another program.
According to the assignment we have to understand what are the background of the Eastern State
University and problem they are facing. And what type of SDLC models we can use to the
university.

pg. 4
 System Analysis and Design

Task 1.1 (P1.1)

Evaluate different system Development Lifecycle models
Model represent reality. Just as a picture is worth thousand words, most system models are
pictorial representation of reality. Using the models, can have better understanding of the
proposed system.
The systems development life cycle (SDLC) is a conceptual model used in project management
that describes the stages involved in an information system development project, from an initial
feasibility study through maintenance of the completed application. In here customer describes
the vision for the system to the developer. This idea is transformed into sketches and drawings
that are shown to the customer and refined until the customer agrees. Develop the blue print.
Build the system.
Why we need SDLC
 SDLC models program development is faster when programmers come together to create
the workflow instead of going through a lot of user inputs and requirements.
 Developers can work on the problem and create a solution based on the need.
 With an SDLC Model, developers can take clear idea on what should be or shouldn’t be
built.
 With an SDLC Model, programs can have a documentation of development, structure and
even coding.
 Aside from longer lifespan of an SDLC modeled program, every created program could
serve be used in another program.

There are so many SLDC system currently we are using. So now I’m going to describe all the
models and their qualities.
Waterfall Model
The linear or the waterfall cycle is a development process that center around planed work and
best suited for project where the requirements can be clearly defined. The linear cycle group
development activities in the sequence of consecutive phases where each phase itself is made up
of more details activities. The waterfall cycle is usually with structured team and documentation
system. Team members are assigned to specific phases and tasks and organized to produce
specific documents. Documents flows also highly structured. Documents produced at the end of
one phase must be available for the input of the next stage.
 By Royce 1970
 A sequential software development model
 Development is flowing steadily downwards (like a waterfall)
 Phases;
 Requirements analysis
 Design

pg. 5
 System Analysis and Design

 Implementation
 Testing (validation)
 Integration
 Maintenance

 Requirement Analysis
The waterfall cycle begins with the concept formation. The first is problem definition
which lead to the project goal. The second is feasibility analysis. This determines feasible
way to achieve this goal.
 Problem definition
This problem definition will be the most important phase. It provides the broad
statements of the user requirements in the user’s world team and sets the direction
to the whole project.
 Feasibility study
Part of requirement analysis phase is feasibility study which process one or more
conceptual solution to the problem set for the project. These solution must be
feasibility and preferred solution must be accepted. Three thing must be done to
establish feasibility there are;
1. Technical feasibility
2. Operational feasibility
3. Economic feasibility
 Design
This phase produces a design specification for the new system. There are many thing to
be done here designers must select the equipment’s needed to implement the system they
also must specify new programs, databases or changes to the existing programs and
database. System design usually proceeds in two steps
1. Broad design
2. Detail design
 Implementation
Components built during the development are put into operational use. Usually this
means the new and old systems are running parallel for some times to complete the
changeover users must be trained in the new system environment.
 Testing
System testing is recognized as an important part in quality assurance activities. Testing
proceeds in parallel with system design. Testing proceeds in parallel with system design.
 Maintenance
Maintenance is necessary to eliminate errors in system during its working life. Normally
in the waterfall process only corrective type of maintenance are allowed.

pg. 6
 System Analysis and Design

Waterfall Model cont.

 Non-iterative development approach
 Linear and sequential approach
 Structured system analysis and design method
 Start with Requirement analysis
 Next stage initiate after complete previous stage
 Input for the next stage will be the output of previous stage.

Output of waterfall model

 Requirement document
 Project plan
 System design document
 Detailed design document
 Test plan and test report
 Final code
 Software manuals (user manual, installation manual etc.)
 Review report

Figure 1 (waterfall Model)

pg. 7
 System Analysis and Design

Advantages Disadvantages
Simple and easy to understand and use. No working software is produced until date
during the life cycle.
Easy to manage, due to the rigidity of the Not a good model for complex and object
model. Each phase has specified liberals and oriented projects.
review process.
Completed one at a time work and phases Poor model for long and anomie project.
are processed. Work for smaller project.
Requirement are very well understood. Not suitable for the project where
requirement are at a moderate to high risk of
changing. So risk and uncertainty is high
with this process model.
Table 1 (Advantages and Disadvantages of waterfall model)

RAD Model
Rapid application development (RAD) is both a general term used to refer to alternatives to the
conventional waterfall model of software development as well as the name for James Martin's
approach to rapid development. In general, RAD approaches to software development put less
emphasis on planning tasks and more emphasis on development. In contrast to the waterfall
model, which emphasizes rigorous specification and planning, RAD approaches emphasize the
necessity of adjusting requirements in reaction to knowledge gained as the project progresses.
This causes RAD to use prototypes in addition to or even sometimes in place of design
specifications. RAD approaches also emphasize a flexible process that can adapt as the project
evolves rather than rigorously defining specifications and plans correctly from the start.

The phases in the rapid application development (RAD) model are:

 Business modeling: The information flow is identified between various business

functions.
 Data modeling: Information gathered from business modeling is used to define data
objects that are needed for the business.
 Process modeling: Data objects defined in data modeling are converted to achieve the
business information flow to achieve some specific business objective. Description are
identified and created for CRUD of data objects.

pg. 8
 System Analysis and Design

 Application generation: Automated tools are used to convert process models into code
and the actual system.
 Testing and turnover: Test new components and all the interfaces.

Figure 2 (RAD Model)

Advantages Disadvantages
Reduced development time. Depends on strong team and individual
performances for identifying business
requirements.
Increases reusability of components Only system that can be modularized can
be built using RAD
Quick initial review occur Require highly skilled developers/designers.
Encourages customer feedback integration High dependency on modeling skills
from very beginning solves a lot of
integration issues
Inapplicable to cheaper projects as cost of
modeling and automated code generation is
very high.

pg. 9
 System Analysis and Design

Table 2 (Advantages and Disadvantages RAD

Model)

Prototyping Model
The basic idea here is that instead of freezing the requirements before a design or coding can
proceed, a throwaway prototype is built to understand the requirements. This prototype is
developed based on the currently known requirements. By using this prototype, the client can get
an “actual feel” of the system, since the interactions with prototype can enable the client to better
understand the requirements of the desired system.  Prototyping is an attractive idea for
complicated and large systems for which there is no manual process or existing system to help
determining the requirements. The prototype are usually not complete systems and many of the
details are not built in the prototype. The goal is to provide a system with overall functionality.

Figure 3 (Prototyping Model)

Advantages Disadvantages
Users are actively involved in the Leads to implementing and then repairing
development. way of building systems.

Since in this methodology a working model Practically, this methodology may increase
of the system is provided, the users get a the complexity of the system as scope of the
better understanding of the system being system may expand beyond original plans.
developed.
Errors can be detected much earlier. Incomplete application may cause
application not to be used as the full system
was designed.

Quicker user feedback is available leading Incomplete or inadequate problem analysis.

pg. 10
 System Analysis and Design

to better solutions.
Missing functionality can be identified
easily.
Confusing or difficult functions can be
identified
Requirements validation, Quick
implementation of, incomplete, but
functional, application.

Table 3 (Advantages and Disadvantages of Prototyping)

Spiral Model
Recent model proposed by Boehm. Activities are organized such a way like spiral. Radial
dimension – cumulative cost incurred in accomplishing the steps dome. Angular dimension -
progress made in completing each cycle of the spiral. Each cycle in the spiral begins with the
identification of objectives and possible alternatives. Evaluate alternatives, analyses risks and
uncertainties. The next step is to develop strategies that resolve the uncertainties and risks which
involve activities such as benchmarking, simulation and prototyping. Next, the software is
developed by keeping in mind the risks. Finally the next stage is planned. The development
spiral consists of four quadrants as shown in the figure above. Quadrants
1. Determine objectives, alternatives, and constraints.
2. Evaluate alternatives, identify, and resolve risks.
3. Develop, verify, next-level product. Quadrant
4. Plan next phases.

 When to use Spiral model:

 When costs and risk evaluation is important

 For medium to high-risk projects
 Long-term project commitment unwise because of potential changes to economic
priorities
 Users are unsure of their needs
 Requirements are complex
 New product line
 Significant changes are expected (research and exploration)

pg. 11
 System Analysis and Design

Figure 4 (Spiral Model)

Advantages Disadvantages
High amount of risk analysis hence, Can be a costly model to use.
avoidance of Risk is enhanced.
Good for large and mission-critical projects. Risk analysis requires highly specific
expertise.
Strong approval and documentation control. Project’s success is highly dependent on the
risk analysis phase.
Additional Functionality can be added at a Doesn’t work well for smaller projects.
later date.
Software is produced early in the software life
cycle.
Table 4 (Advantages and Disadvantages of spiral Model)

pg. 12
 System Analysis and Design

Iterative Model
First step: simple initial implementation is done for a subset of the overall problem. Iteratively
enhances the evolving versions until the full system is implemented. At each iteration, design
modifications are made and new functional capabilities are added. The basic idea behind this
method is to develop a system through repeated cycles (iterative) and in smaller portions at a
time (incremental).

Figure 5 (Iterative Model)

When to use iterative model:

 Requirements of the complete system are clearly defined and understood.

 When the project is big.
 Major requirements must be defined; however, some details can evolve with time.

Advantages Disadvantages
Only create a high-level design of the Each phase of an iteration is rigid with no
application overlaps
Can get the reliable user feedback. Costly system architecture or design
issues may arise because not all
requirements are gathered up front for the
entire lifecycle
In iterative model less time is spent on
documenting and more time is given for
designing.

pg. 13
 System Analysis and Design

Table 5 (Advantages and Disadvantages of Iterative Model)

Agile Model
Agile model believes that every project needs to be handled differently and the existing methods
need to be tailored to best suit the project requirements. A combination of iterative and
incremental process models. Agile Methods break the product into small incremental builds,
these builds are provided in iterations.

Figure 6 (Agile Model)

Advantages
Customer satisfaction by rapid, continuous
delivery of useful software.
People and interactions are emphasized rather
than process and tools. Customers, developers
and testers constantly interact with each other
Working software is delivered frequently
(weeks rather than months).
Face-to-face conversation is the best form of
communication.
Close, daily cooperation between business
Disadvantages
In case of some software deliverables,
especially the large ones.
There is lack of emphasis on necessary
designing and documentation
The project can easily get taken off track if
the customer representative is not clear what
final outcome that they want.
Only senior programmers are capable of
taking the kind of decisions required during
the development process

pg. 14
 System Analysis and Design

people and developers.

Continuous attention to technical excellence
and good design.
Regular adaptation to changing
circumstances.
Even late changes in requirements are
welcomed.

Table 6 (Advantages and Disadvantages of Agile Model)

When to use agile model:

 When new changes are needed to be implemented. The freedom agile gives to change is
very important. New changes can be implemented at very little cost because of the
frequency of new increments that are produced.
 To implement a new feature the developers need to lose only the work of a few days, or
even only hours, to roll back and implement it.
 Unlike the waterfall model in agile model very limited planning is required to get started
with the project. Agile assumes that the end users’ needs are ever changing in a dynamic
business and IT world. Changes can be discussed and features can be newly effected or
removed based on feedback.
 Both system developers and stakeholders alike, find they also get more freedom of time
and options than if the software was developed in a more rigid sequential way

Planning Phase: Requirements are gathered during the planning phase.

Risk Analysis: In the risk analysis phase, a process is undertaken to identify risk and alternate
solutions.  A prototype is produced at the end of the risk analysis phase. If any risk is found
during the risk analysis then alternate solutions are suggested and implemented.

Engineering Phase: In this phase software is developed, along with testing at the end of the
phase. Hence in this phase the development and testing is done.

Evaluation phase: This phase allows the customer to evaluate the output of the project to date
before the project continues to the next spiral.

pg. 15
 System Analysis and Design

Dynamic system Development Method

Another approach to system development. Develops the system dynamically. This methodology
is independent of tools. A Rapid Application Development method that uses incremental
prototyping. Useful for the systems to be developed in short time span and where the
requirements cannot be frozen at the start of the application building. Analysis, design and
development phase can overlap. Requirements evolve with time

Five-phase life cycle

 Feasibility study
 Business study
 Functional Model Iteration
 Design and Build Iteration
 Implementation

DSDM Stages
 Feasibility study
 Problem is defined
 Technical feasibility of the desired application is verified
 Check suitability for the RAD
 Only if application is suitable for the RAD, development process
continues.
 Business study
 Overall business study of the desired system is done
 Business requirements are specified
 Then the basic architectural framework of the desired system is prepared
 Maintainability level identified to provide quality control activities
 Functional Model Iteration
 Building the prototype iteratively and getting it reviewed from the users to
bring out the requirements of the desired system
 The prototype is improved through demonstration to the user, taking the
feedback and incorporating the changes
 This cycle is repeated generally twice or thrice until a part of functional
model is agreed upon.
 The end product of this phase is a functional model consisting of analysis
model and some software components containing the major functionality
 Design and Build Iteration
 Ensure that the prototypes are satisfactorily and properly engineered to
suit their operational environment
 The software components designed during the functional modeling are
further refined till they achieve a satisfactory standard.

pg. 16
 System Analysis and Design

 The product of this phase is a tested system ready for implementation.

 Implementation
 The users are trained and the system is actually put into the
operational environment

Figure 7 (DSDM Model)

pg. 17
 System Analysis and Design

Task 1.2 (P1.2, M3.3)

Create a document for the lifecycle stages and do the presentation
In many ways, building an information system is similar to building a house.
1. The owner describes the vision for the house to the developer.
2. This idea is transformed into sketches and drawings that are shown to the owner and
refined until the owner agrees that the pictures depict what owner wants.
3. A set of detailed blueprints is developed that presents much more specific information
about the house.
4. Finally, the house is built following the blueprints—and often with some changes and
decisions made by the owner as the house is erected.
Building an information system using the SDLC follows a similar set of four fundamental
phases.
 Planning
 Analysis
 Design
 Implementation
Each phase is itself composed of a series of steps, which rely on techniques that produce
deliverables. Different projects may use different parts of the SDLC or approach the SDLC
phases in different ways, but all projects have elements of these four phases. These deliverables
in turn are used in the implementation phase to guide the creation of the actual system. Each
phase refines on the work done previously.
Planning
The planning phase is the fundamental process of understanding why an information system
should be built and determining how the project team will go about building it. It has two steps:
1. During project initiation the system’s business value to the organization is identified—
how will it lower costs or increase revenues? Most ideas for new systems come from
outside the area. In the form of a system request. A system request presents a brief
summary of a business need, and it explains how a system that supports the need will
create business value. The feasibility analysis examines key aspects of the proposed
project:
 The technical feasibility
 The economic feasibility
 The organizational feasibility
The system request and feasibility analysis are presented to an information systems approval
committee, which decides whether the project should be undertaken.
Analysis

pg. 18
 System Analysis and Design

The analysis phase answers the questions of who will use the system, what the system will do,
and where and when it will be used. During this phase, the project team investigates any current
system, identifies improvement opportunities, and develops a concept for the new system. This
phase has three steps:
1. An analysis strategy is developed to guide the project team’s efforts. Such a strategy
usually includes a study of the current system and its problems, and envisioning ways to
design a new system.
2. The next step is requirements gathering. The analysis of this information—in conjunction
with input from the project sponsor and many other people—leads to the development of a
concept for a new system.
3. The analyses, system concept, and models are combined into a document called the system
proposal, which is presented to the project sponsor and other key decision makers will decide
whether the project should continue to move forward.
Design
The design phase decides how the system will operate in terms of the hardware, software, and
network infrastructure that will be in place; the user interface, forms, and reports that will be
used; and the specific programs, databases, and files that will be needed. Although most of the
strategic decisions about the system are made in the development of the system concept during
the analysis phase, the steps in the design phase determine exactly how the system will operate.
The design phase has four steps:
1. The design strategy must be determined. This clarifies whether the system will be
developed by the company’s own programmers, whether its development will be outsourced
to another firm, or whether the company will buy an existing software package.
2. This leads to the development of the basic architecture design for the system that describes
the hardware, software, and network infrastructure that will be used. In most cases, the
system will add to or change the infrastructure that already exists in the organization. The
interface design specifies how the users will move through the system and the forms and
reports that the system will use.
3. The database and file specifications are developed. These define exactly what data will be
stored and where they will be stored.
4. The analyst team develops the program design, which defines the programs that need to be
written and exactly what each program will do.
Implementation
The final phase in the SDLC is the implementation phase, during which the system is actually
built. This is the phase that usually gets the most attention, because for most systems it is the
longest and most expensive single part of the development process. This phase has three steps:

pg. 19
 System Analysis and Design

1. System construction is the first step. The system is built and tested to ensure that it
performs as designed.
2. The system is installed. Installation is the process by which the old system is turned off
and the new one is turned on.
3. The analyst team establishes a support plan for the system. This plan usually includes a
formal or informal post-implementation review, as well as a systematic way for
identifying major and minor changes needed for the system.
So these are the phases of SDLC. With help of this stages we can built very good SDLC Model
for the client.
Usage of SDLC
 SDLC models program development is faster when programmers come together to create
the workflow instead of going through a lot of user inputs and requirements.
 Developers can work on the problem and create a solution based on the need.
 With an SDLC Model, developers can take clear idea on what should be or shouldn’t be
built.
 With an SDLC Model, programs can have a documentation of development, structure and
even coding.
 Aside from longer lifespan of an SDLC modeled program, every created program could
serve be used in another program.

The advantages of SDLC.

 The existing system is evaluated.
 The new system requirements are defined.
 The proposed system is designed. Plans are laid out concerning the physical construction,
hardware, operating systems, programming, communications, and security issues.
 May generate specification for a production application.
 Environment to resolve unclear objectives.
 Encourage innovation and flexible designs.

pg. 20
 System Analysis and Design

Task presentation

Figure 8 (Task presentation)

Figure 9 (Task presentation)

pg. 21
 System Analysis and Design

Figure 10 (Task presentation)

Figure 11(Task presentation)

pg. 22
 System Analysis and Design

Figure 12 (Task presentation)

Figure 13 (Task presentation)

pg. 23
 System Analysis and Design

Figure 14 (Task presentation)

Figure 15 (Task presentation)

pg. 24
 System Analysis and Design

Figure 17 (Task presentation)

Figure 18 (Task presentation)

Figure 19 (Task presentation)

pg. 25
 System Analysis and Design

Task 1.3 (M1.1)

Select the one of SDLC Model suited to the scenario and justify the
selection
According to the scenario for the Eastern State University (ESU) RAD model will be more
suitable. Rapid application development (RAD) is an incremental software development process
model that emphasize and exactly short development cycle. The RAD model is a high speed
adaptation of linear sequential model in which rapid development is achieved by using
component-based construction. If requirements are well understood and project scope is
constrained, the RAD process enables a development team to create a “fully functional System”
within very short time periods. RAD both a general term used to refer to alternatives to the
conventional waterfall model of software development as well as the name for James Martin's
approach to rapid development. In general, RAD approaches to software development put less
emphasis on planning tasks and more emphasis on development. In contrast to the waterfall
model, which emphasizes rigorous specification and planning, RAD approaches emphasize the
necessity of adjusting requirements in reaction to knowledge gained as the project progresses.
This causes RAD to use prototypes in addition to or even sometimes in place of design
specifications. RAD approaches also emphasize a flexible process that can adapt as the project
evolves rather than rigorously defining specifications and plans correctly from the start.

The phases in the rapid application development (RAD) model are:

 Business modeling: The information flow is identified between various business

functions.
 Data modeling: Information gathered from business modeling is used to define data
objects that are needed for the business.
 Process modeling: Data objects defined in data modeling are converted to achieve the
business information flow to achieve some specific business objective. Description are
identified and created for CRUD of data objects.
 Application generation: Automated tools are used to convert process models into code
and the actual system.
 Testing and turnover: Test new components and all the interfaces.

When to use RAD model:

 RAD should be used when there is a need to create a system that can be modularized
in 2-3 months of time.

pg. 26
 System Analysis and Design

 It should be used if there’s high availability of designers for modeling and the budget
is high enough to afford their cost along with the cost of automated code generating
tools.
 RAD SDLC model should be chosen only if resources with high business knowledge
are available and there is a need to produce the system in a short span of time (2-3
months).
 RAD should be used only when a system can be modularized to be delivered in
incremental manner
 It should be used if there.is high availability of designers for modeling.
 It should be used only if the budget permits use of automated code generating tools.
 RAD SDLC model should be chosen only if domain experts are available with
relevant business knowledge.

According to scenario

 RAD model enables rapid delivery as it reduces the overall development time due to
reusability of the components and parallel development.
 RAD works well only if high skilled engineers are available and the customer is also
committed to achieve the targeted prototype in the given time frame. If there is
commitment lacking on either side the model may fail.
 Changing requirements can be accommodated.
 Progress can be measured.
 Iteration time can be short with use of powerful RAD tools.
 Productivity with fewer people in short time.
 Reduced development time.
 Increases reusability of components
 Quick initial reviews occur
 Encourages customer feedback
 Integration from very beginning solves a lot of integration issues.

pg. 27
 System Analysis and Design

Task 1.4 (M2.3)

Discuss the application of the DSMD to the given scenario
What is the DSMD
Another approach to system development. Develops the system dynamically. This methodology
is independent of tools. A Rapid Application Development method that uses incremental
prototyping. Useful for the systems to be developed in short time span and where the
requirements cannot be frozen at the start of the application building. Analysis, design and
development phase can overlap. Requirements evolve with time.

Five-phase life cycle

 Feasibility study
 Business study
 Functional Model Iteration
 Design and Build Iteration
 Implementation

DSDM Stages
 Feasibility study
Problem is defined. Technical feasibility of the desired application is verified. Check
suitability for the RAD. Only if application is suitable for the RAD, development process
continues.
 Business study
Overall business study of the desired system is done. Business requirements are specified. Then
the basic architectural framework of the desired system is prepared. Maintainability level
identified to provide quality control activities
 Functional Model Iteration
Building the prototype iteratively and getting it reviewed from the users to bring out the
requirements of the desired system. The prototype is improved through demonstration to the
user, taking the feedback and incorporating the changes. This cycle is repeated generally twice or
thrice until a part of functional model is agreed upon. The end product of this phase is a
functional model consisting of analysis model and some software components containing the
major functionality
 Design and Build Iteration
Ensure that the prototypes are satisfactorily and properly engineered to suit their operational
environment. The software components designed during the functional modeling are further
refined till they achieve a satisfactory standard. The product of this phase is a tested system
ready for implementation.

pg. 28
 System Analysis and Design

 Implementation
The users are trained and the system is actually put into the operational environment.

Figure 20 (DSDM Diagram)

DSDM Model Advantages
 Active user participation throughout the life of the project and iterative nature of
development improves quality of the product.
 DSDM ensures rapid deliveries.
 Both of the above factors result in reduced project costs

Apply the DSDM to the given scenario

Feasibility study: 1
Here have to work closely with our clients using various analytical techniques to gather
requirements for the intended solution. These are documented and agreed before further
progress is made. Feasibility study is the first and one of importance stage in this
Database life cycle. It is the most labor intensive for the database designer. This stage
involves assessing the informational need of an organization. So that a database can be
designed to meet those needs. To complete this stage we have to ask their needed and
what kind of information we should put. According to the scenario we need to collect the
information and order it step by step. So we have to gather information form the Eastern
State University management and have to find out what type of data they want for their
database.

pg. 29
 System Analysis and Design

Business Study: 2
In this organization we have to study their overall business study of the desired system is
done and their business requirements specification which will helpful to build the system.
Then the basic architectural framework of the system have design and then we have to
give them full maintainability level identified to provide quality control activities.
Functional Model Iteration: 3
Building the prototype iteratively and getting it reviewed from the users to bring out the
requirements of the desired system. The prototype is improved through demonstration to
the user, taking the feedback and incorporating the changes. This cycle is repeated
generally twice or thrice until a part of functional model is agreed upon. The end product
of this phase is a functional model consisting of analysis model and some software
components containing the major functionality.

Design and Build Iteration: 4

From the agreed requirements we produce a detailed functional specification of the
system. This includes detailed designs of all components required and will include
technology specifications, such as environment and server requirements, if required.
Depending on the nature of the requirement, and the project overall, we have to design an
ER diagram for gathered information and may be produced conceptual model this stage.
Now taking all the information we can draw a logical diagram for the client. During the
first part of the logical design, a conceptual model is created base on the needs
assessment performed in stage one. A conceptual model is typically an entity relationship
(ER) diagram. Here we should include cardinality, and relation between every entity.
And Cleary we have to indicate attributes and what the primary keys, the foreign keys
are.
Implementation: 5
Then we take the functional specification and develop the database application
components to defined standards. Where appropriate, ESU is able to test prototypes
during the applications development process in order to provide feedback at key stages.
So this will be the most important section of the database design. Implementation is a
crucial stage in achieving a new system which will fulfill its term of reference without
unsatisfying the user. Plans for the implementation needed to be mead early in the design
phase, long before system is tested and ready for implementation. Do to implement for
the ESU we have to follow below method.
 Planning and control.
 Site preparation
 Education and training
 New equipment
 System testing

pg. 30
 System Analysis and Design

Testing and acceptance: 6

Once it has passed quality assurance, the system is released to our client for beta-testing
prior to a final iteration which includes formal client acceptance testing. In this stage I am
test what are the thing I missed and after testing if there is any miss place I can add it to
the database. So finally I can handle the good database to the ESU management.
According to this step now we have a database design. So we have to check whether we
have included all the information for the design and client requirement is satisfied. For do
that we have to test the system and find out what we have to recreate or added.

Deployment: 7

Work with the client to determine the most appropriate method of deployment for the
project. This may involve everything from a packaged application deployed on a CD
through to a full business change programmed. So in this stage I can develop the database
to the ESU. According to this stage after testing if we forgot some information we can
add it or otherwise we have to give space for do any future development to the design and
if we need it we can add it to the database
Support and maintenance: 8
All of our work is covered by warranty, but additional on-going database support and
maintenance agreements ensure that our system is carefully monitored and running
smoothly on a daily basis. This stage every work is almost finish and finally I have to
give the user support and maintenance guidance for the ESU management. After handing
over the database with support these thing they can maintain the database without any
problem. This is the most important stage of the database life cycle. After we design a
database we should maintain it properly. Otherwise it will not give full output to the
client. So we have to provide a user guidance how to maintain the database. With help of
that they can maintain good database.

pg. 31
 System Analysis and Design

Task 1.5 (D1.1)

Different type of fact finding techniques.

Introduction
Fact-finding is the formal process of using research, interviews, questionnaires, sampling, and
other techniques to collect information about systems, requirements, and preferences. It is also
called information gathering or data collection. Tools, such as data and process models,
document facts, and conclusions are drawn from facts. If we can't collect the facts, we can't use
the tools. Fact-finding skills must be learned and practiced. Systems analysts need an organized
method of collecting facts.
What are the fact finding method
 Sampling of existing documentation, forms, and databases.
 Research and site visits.
 Observation of the work environment.
 Questionnaires.
 Interviews.
Among these fact finding methods I am going to choose

1. Sampling of existing documentation, form and database.

 First we have to document the analyst should seek out is the organizational
chart.
 Then the analyst may want to trace the history that led to the project.
To achieve, the analyst may want to collect and review documents that describe
the problem. These include interoffice memoranda, studies, minutes, suggestion
box notes, customer complaints, and reports that document the problem area.
Accounting records, performance reviews, work measurement reviews, and other
scheduled operating reports. Information systems project requests – past and
present. There are usually documents that describe the business function being
studied or designed. These documents may include, The Company mission
statement and strategic plan. Formal objectives for the organization sub-units
being studied. Policy manuals that may place constraints on any proposed system.
Standard operating procedures (SOPs), job outlines, or task instructions for
specific day-to-day operations. Completed forms that represent actual transactions
at various points in the processing cycle. Samples of manual and computerized
databases. Samples of manual and computerized screens and reports.
 All documentation collected should be analyzed to determine currency of the
information.
 Don't discard outdated documentation.

pg. 32
 System Analysis and Design

 As we review existing documents, take notes, draw pictures, and use systems
analysis and design tools to model what we are learning or proposing for the
system.
 Because it would be impractical to study every occurrence of every form,
analysts normally use sampling techniques to get a large enough cross section
to determine what can happen in the system.
 Experienced analysts avoid the pitfalls of sampling blank forms -- they tell
little about how the form is used, not used, or misused.
 When studying documents or records from a database table, you should study
enough samples to identify all the possible processing conditions and
exceptions.
 Determine Sample Size.
 Selecting the Sample

2. Research and site visits.

 My second fact-finding technique is to thoroughly research the application
and problem.
 Computer trade journals and reference books are a good source of
information.
 Exploring the internet and World Wide Web (WWW) via your personal
computer can provide you with an immeasurable amounts of information.
 A similar type of research involves visiting other companies or departments
that have addressed similar problems.
 Memberships in professional societies such as Data Processing Management
Association (now known as AITP), or Association for Information Systems
(AIS) among others can provide a network of useful contacts.
For the scenario above tow fact finding methods are more suitable. Because,
 Because this fact finding methods is most suitable for the university.
 As university they have to keep student record and other important details which
are useful to conduct the university smoothly.
 So this fact finding method will be helpful to gathering the information to build
the system.
 And also we no need to give extra time for the collect the information.
 Easily we can find the information.
 We can go and visit the university.
 We can use the internet to refer the data.
 We can shard the details in between the customer.

pg. 33
 System Analysis and Design

Other fact finding methods.

3. Observation of the Work Environment
 Observation is one of the most effective data-collection techniques for obtaining
an understanding of a system
 This technique is often used when the validity of data collected through other
methods is in question or when the complexity of certain aspects of the system
prevents a clear explanation by the end-users.
 Observation Advantages
 Data gathered by observation can be highly reliable.
 The systems analyst is able to see exactly what is being done.
 Observation is relatively inexpensive compared with other fact-
finding techniques.
 Observation allows the systems analyst to do work measurements.

 Observation Disadvantages
 Because people usually feel uncomfortable when being watched,
they may unwittingly perform differently when being observed.
 The work being observed may not involve the level of difficulty or
volume normally experienced during that time period.
 Some systems activities may take place at odd times, causing a
scheduling inconvenience for the systems analyst.
 The tasks being observed are subject to various types of
interruptions.
4. Questionnaires
 Questionnaires are special-purpose documents that allows the analyst to collect
information and opinions from respondents.
 The document can be mass produced and distributed to respondents, who can then
complete the questionnaire on their own time.
 Questionnaires allow the analyst to collect facts from a large number of people
while maintaining uniform responses.
 When dealing with the large audience, no other fact-finding technique can
tabulate the same facts as efficiently.
 Questionnaires Advantages
 Most questionnaires can be answered quickly.
 People can complete and return questionnaires at their
convenience.
 Questionnaires provide a relatively inexpensive means for
gathering data from a large number of individuals.
 Questionnaires allow individuals to maintain anonymity.
 Individuals are more likely to provide the real facts, rather than
telling you what they think their boss would want them to.
 Responses can be tabulated and analyzed quickly.

pg. 34
 System Analysis and Design

 Collecting Facts by Using Questionnaires

 Questionnaires Disadvantages
 The number of respondents is often low.
 There's no guarantee that an individual will answer or expand on
all of the questions.
 Questionnaires tend to be inflexible.
There are two formats for questionnaires,
1. Free-format questionnaires
This type of question offer the respondent greater latitude in the answer. A question is
asked, and the respondent records the answer in the space provided after the question.
2. Fixed-format questionnaires
Fixed-format questionnaires contain questions that require specific responses from
individuals. Given any question, the respondent must choose from the available answers.

5. Interviews
 The personal interview is generally recognized as the most important and most
often used fact-finding technique.
 Interviews are a fact-finding technique whereby the systems analysts collects
information from individuals face to face.
 There are two roles assumed in an interview. 1 The systems analyst is the
interviewer, responsible for organizing and conducting the interview. 2 The
system user, system owner, or adviser is the interviewee, who is asked to respond
to a series of questions.
 Interviews Advantages
 Interviews give the analyst an opportunity to motivate the
interviewee to respond freely and openly to questions.
 Interviews allow the systems analyst to probe for more feedback
from the interviewee.
 Interviews permit the systems analyst to adapt or reword questions
for each individual.
 Interviews give the analyst an opportunity to observe the
interviewee's nonverbal communication.
 Interviews Disadvantages
 Interviewing is a very time-consuming, and therefore costly, fact-
finding approach.
 Success of interviews is highly dependent on the systems analyst's
human relations skills.
 Interviewing may be impractical due to the location of
interviewees.
6. Rapid Application Development (RAD)

pg. 35
 System Analysis and Design

 Rapid Application Development is gaining popularity as a fact-finding technique

for discovering user requirements.
 This technique allows analysts to quickly create mock forms and tables to
simulate the implemented system.
 Users can suggest changes to the prototype real-time and in most cases watch as
the analyst tweaks the software to produce the desired look and feel.
 This process may take several iterations to correctly capture the functions
necessary to automate the required business processes.
 Once the prototype is completed, you have the basis for a user’s manual, a
requirements specification, and a template for a test plan.

pg. 36
 System Analysis and Design

Conclusion
This report has identified what are the different systems lifecycle models available and then
discuss the importance of each staged lifecycle in a systems. Then select one of the SDLC for the
Eastern State University and clearly mention why chose this model to crate this system. Then
separately discuss Dynamic System Design Methodology and discuss the application of the
DSDM. Then describe different fact finding techniques that were used in the collecting data and
then select the two fact finding techniques.

pg. 37
 System Analysis and Design

Reference

pg. 38