unit 6
unit 6
Maintenance System
and review analysis
SDLC
implementation System design
System
System testing
development
5. System testing:
System testing is an investigation conducted to solve
stakeholders with information about the quality of the product or
services under test. System testing can also be stated as the process of
validating and verifying that a software program or product.
Some testing methods are given below:
• White box testing : white box testing of software is predicted (guess)
on close examination of procedural details. White box testing is used
when the tester has access(use) to the internal data structures and
algorithms including code. It is also called glass box testing.
• Black box testing: Black box testing treats the software as a “black
box”- without any knowledge of internal implementation. It is also
called functional testing because it tests whether a system is functioning
or not. Testing stages are: i) Unit testing ii) System testing iii) Acceptance
testing.
6. Implementation:
implementation involves the installed system, converting from
the old system to the new one and training the users. The new system
is installed and operated with old system until it has been checkout.
Then the old system is then removed from operation and new system
takes from thereafter(later).
The implementation operation is divided in 4 major categories :
a .Direct conversion: DC in which old system is stopped and new system
comes into effects immediately .
b. Parallel conversion: PC in which old system and new system is
operated parallel in an action.
c. Phased conversion: PC in which new system is introduced partially
one after another.
d. Pilot conversion: PC in which the new system is installed for a few
users, who evaluate it and help decide whether it is suitable for the rest
of the system to implement or not.
7. Maintenance and review:
When the system is implemented , maintenance and
modification begin. The software and hardware also requires periodic
maintenance so as to keep in tune with design specification and to
innovate(develop) new ideas into the system. The contents of the
review will include: i. Objectives ii. Cost iii. Performance iv.
Standards v. recommendation
Types of maintenance:
a) Corrective maintenance: It corrects the run time errors during
operation.
b) Adaptive maintenance: It modifies or adds new features in the
system according to the environment change.
c) Perfective maintenance: It makes the system perfect , up-to-date
and improve the life of the system.
Symbols Description
Decision
To make logical decision (True or False)
Flow lines
To indicate flow of flowchart
2. Algorithm: Algorithm is one of the most basic tools used for solving problem. It is defined as
the finite -l;ldt_ sequence -s|d_ of instruction for solving a problem . It consists of
stepwise list of English statements making sequence procedure -k|lqmof_.
3. Pseudo code: Pseudo code is a kind of algorithm for solving a problem. The instructions of
pseudo code are written by using English phrase -jfSo_ and mathematical expression.
4. Decision Table: The decision to be made in the program are presented in a tabular form,
which is known as decision table. A decision generally consists of two parts: condition and
action. For example , to find the maximum of among 3 numbers using decision table.
A>B F F T T
Condition
B>C F T F T
A is maximum X X X T
B is maximum X T X X
Action
C is maximum T X X X
5. Decision Tree: It is the conversion -ablnPsf]_ of the decision table in terms of tree. It
makes the decision easier to understand. Decision tree is more user-friendly -cg's"n_ because
it provides a graphical hierarchical -kbfg'qmd_ diagrammatic view of condition and action.
Example : find the maximum of among 3 different numbers using decision tree.
T A is Max
(A>B>C)
T B is Max
(B>C)
F B or C is Max
F C is Max
6. Data Flow Diagram(DFD): It is one of the most important tools used by system analyst -
ljZn]ifs_ in SDLC phase. It is actually a process of presenting the working of system in terms of
some diagrams. DFD is also the logical diagram to describe the flow of data in side the
components of system. The main components are : process, data store , data flow , external
entities -PsfO_. Some of the symbols used in DFD are given below:
Symbol name Use Diagram
Examples:
Computer Purchase.dat
Supplier Price
External files
External entities Process
7. Context diagram:
It is the highest level of DFD. It contains only one process,
representing the entire system, the process is given the symbol
circle. The external entities are denoted by rectangle. The flow of
data is described by arrow.
8. ERD( Entity Relationship Diagram) : The diagrammatic representation of entities attributes and
their relationship is described by E-R diagram. The E-R diagram is an overall logical structure of a
database that can be expressed graphically. It was developed to facilitated database design and
their simplicity. The basic components of ER diagram are given below:
1. Entity: An entity is a “thing” or “object” in the real world. For example , if student is an
entity, is identified by registration number. It is represented by rectangle.
student
2. Attribute: Attributes are properties possessed by an entity or relationship. For e.g. std_no,
std_name, std_sub are the attributes of the entity student. Attribute is represented by oval.
Roll no
Teach
4. Lines: The flow of information is indicated by the lines in ER-diagram. It is simply a line. It is a
connector of entities, attributes and relationship.
Example of ER-diagram:
Name ID Name
Address
Subject
Class Faculty
1. Waterfall model:
This model is sometimes called classic life cycle
because it suggest a systematic sequential approach to software
development that begins with customer specification(requirement)
and progress through planning, modeling, construction etc. It is only
appropriate if all the requirements are known. It is an oldest type of
model for software engineering.
Merits (Advantages):
i. It is simple model suitable for small size project.
ii. It is les expensive.
Fig. Waterfall model
Demerits(disadvantages):
i. It is not suitable for large size project.
ii. It has lack of proper documentation.
iii. It has no back track mechanism.
2. Prototyping model: This is most suitable for new system where there is no clear
idea of the requirements, inputs and outputs. It is the iterative (loop) process of
system development. Using prototyping, programmer can build early version of
system. These systems are then continuously modified until the user is satisfied.
Demerits:
vi. Because of the iterative nature of prototyping, there is no definite
deliverable or completion deadline.
vii. Code inefficiencies my be a drawback in term of functionality.
3. Spiral model: This is the latest model of software development. In this model,
process is represented as a spiral rather than a sequence of activities. The
activities in SDLC are organized in a spiral structure that has many cycle which
starts from the center of the spiral and goes out as it progress and becomes
matured. Each of the complete spiral segment is divided into four different
attribute known as – planning, risk analysis, software development and user
evaluation.
Or Planning
Merits:
i. It emphasizes (highlights) risk.
ii. It emphasizes quality.
iii. It emphasizes risk reduction.
iv. It is effective for regular updating the system.
v. Effective user feedbacks.
Demerits:
i. Full scale risk analysis require training, skill, and large expense,
so it may appropriate only for large projects.
ii. The model is relatively untested.
iii. There is minimum documentation generated.
End of unit 6