1.

Introduction
Analysis and Design
Objects

• Systems Development Life Cycle (SDLC)

Methodolody
• Models

Analysis and Design of IS 2

• A systems analyst may be involved with any
or all of these systems at each organization
level
Strategic
Level

Higher Level

Knowledge
Level

Operational
Level

Analysis and Design of IS 3

• Information systems are developed for different purposes, depending
on the needs of the business.
• Operational
 Transaction Processing Systems (TPS)
• Knowledge Level
 Office Automation Systems (OAS)
 Knowledge Work Systems (KWS)
• Higher Level
 Management Information Systems (MIS)
 Decision Support Systems (DSS)
 Expert Systems (ES)
• Strategic Level
 Executive Support Systems (ESS)
 Group Decision Support Systems (GDSS)
 Computer-Supported Collaborative Work Systems (CSCWS)

Analysis and Design of IS 4

The seven phases of the systems
development life cycle

Analysis and Design of IS 5

Phase 1: Identifying and gathering requirements

• Critical to the success of the rest of

the project, because no one wants to
waste time addressing the wrong
problem.
• Problems – generally the reason the
analyst was called in in the first place.
• Opportunities – situations that the
analyst believes can be improved
through the use of computerized
information systems.
• Objectives – how can the business
reach its objectives by addressing
specific problems or opportunities.

• The people: users, analysts, and

systems managers.

Analysis and Design of IS 6

Analysis and Design of IS 7
• Activity:
 Interviewing user management
 Summarizing the knowledge obtained
 Estimating the scope of the project
 Documenting the results

• Output:
 Feasibility report containing problem definition
and objective summaries from which
management can make a decision on whether to
proceed with the proposed project

Analysis and Design of IS 8

Phase 2: Planning – Feasibility study

• Project management and product management are part of the

planning phase.
Examples of these are:
 Scheduling projects
 Estimation of costs
 Provisioning
 Allocation of resources (both human and material)
 Capacity planning

• Plans, schedules, cost estimates, and procurement

requirements are some of the outputs of the planning phase. To
ensure all perspectives are represented, Project Managers and
Development staff should work with Operations and Security
staff to account for all the departmental needs.

Analysis and Design of IS 9

• Feasibility study
 To define and document software needs - ‘Software
Requirement Specification’ document also known as ‘SRS’
document.
 There are mainly five types of feasibilities checks:
 Economic: Can we complete the project within the budget or not?
 Legal: Can we handle this project as cyber law and other
regulatory framework/compliances.
 Operation feasibility: Can we create operations which is expected
by the client?
 Technical: Need to check whether the current computer system
can support the software
 Schedule: Decide that the project can be completed within the
given schedule or not.

Analysis and Design of IS 10

 • A Feasibility Analysis Includes Tests for
Economic, Technical, and Operational
Success.

Analysis and Design of IS 11

Phase 3: Design

• There are two kinds of design documents

developed in this phase:
 High-Level Design (HLD)
 Brief description and name of each module
 An outline about the functionality of every module
 Interface relationship and dependencies between
modules
 Database tables identified along with their key elements
 Complete architecture diagrams along with technology
details

Analysis and Design of IS 12

  Low-Level Design (LLD)
 Functional logic of the modules
 Database tables, which include type and size
 Complete detail of the interface
 Addresses all types of dependency issues
 Listing of error messages
 Complete input and outputs for every module

Analysis and Design of IS 13

• Use-Case Diagrams

Analysis and Design of IS 14

• Use Case Description

Analysis and Design of IS 15

 Level 0 Diagram

Context Diagram

Look at balancing of
Data
Flows between the
two
diagrams
Analysis and Design of IS 16
 Level 1 Diagram
Explosion of FILL ORDER Process

Level 0 Diagram

Look at balancing of
Data
Flows between the two
diagrams
Analysis and Design of IS 17
 Level 1 Diagram
Explosion of APPLY PAYMENT Process

Level 0 Diagram

Look at balancing of
Data
Flows between the two
diagrams
Analysis and Design of IS 18
 • Data
Dictionary

Analysis and Design of IS 19

• ERD Elements

Analysis and Design of IS 20

• Relationship types

Analysis and Design of IS 21

• User Interface Design
 Input Design
 Menu Design
 Output Design

Analysis and Design of IS 22

• Database Design

Analysis and Design of IS 23

• System Architecture

Analysis and Design of IS 24

Phase 4: Coding
• Developers start build the entire system by
writing code using the chosen programming
language.
 In the coding phase, tasks are divided into units or
modules and assigned to the various developers.
 It is the longest phase of the Software Development
Life Cycle process.
• Developer needs to follow certain predefined
coding guidelines. They also need to use
programming tools like compiler, interpreters,
debugger to generate and implement the code.

Analysis and Design of IS 25

Phase 5: Testing
• Once the software is complete, and it is deployed in the
testing environment. The testing team starts testing the
functionality of the entire system. This is done to verify
that the entire application works according to the
customer requirement.
• During this phase, QA and testing team may find some
bugs/defects which they communicate to developers. The
development team fixes the bug and send back to QA for
a re-test. This process continues until the software is bug-
free, stable, and working according to the business needs
of that system.

Analysis and Design of IS 26

• SDLC’s testing phase is considered to be one of the most crucial
phases. Quality software cannot be delivered without testing. Many
types of testing are necessary to measure quality which includes:
 Performance testing
 Unit testing (functional tests)
 Code quality
 Security testing
 Integration testing

• Automating tests is the best way to ensure that they are run regularly
and are never skipped because of expediency. With Continuous
Integration tools, such as Codeship, tests can be automated. The
developed software is ready for deployment in a production
environment after it has been tested appropriately.

Analysis and Design of IS 27

Software Quality Assurance
• Quality should be measured via a set of the following attributes:
 Portability: the ability of the software to be transferred easily from one
computer to another.
 Efficiency: the ability of the software to perform with minimum use of
computer resources.
 Usability: the ability of the software to be easily understood and used
by human users.
 Testability: the ability of the software to be easily verified by execution.
 Understandability: the ability of the software to be read by a software
maintained.
 Modifiability: the ability of the software to be revised by a software
maintained.

Analysis and Design of IS 28

• Risk Management
 Everyone involved in the software process
 managers,
 software engineers, and
 Customers
 Project Risks
 Technical Risks
 Business Risks
 Categorization of risks
 Risk identification

Analysis and Design of IS 29

Phase 6: Installation/Deployment
• Once the software testing phase is over and no bugs or errors
left in the system then the final deployment process starts.
• Based on the feedback given by the project manager, the final
software is released and checked for deployment issues if any.
• UAT (User Acceptance testing) is done depending on the
customer expectation.
• Activity:
 Train users
 Analyst plans smooth conversion from old system to new
system
 Review and evaluate system
• Output:
 Trained personnel
 Installed system

Analysis and Design of IS 30

• Installation and Evaluation
 Operational and Test Environments
 Training
 File Conversion
 Post-Implementation Evaluation
 Final Report to Management

File Conversion &

Analysis and Design of IS System Changeover 31
Phase 7: Maintenance

• Once the system is deployed, and customers

start using the developed system, following 3
activities occur
 Bug fixing – bugs are reported because of some
scenarios which are not tested at all
 Upgrade – Upgrading the application to the newer
versions of the Software
 Enhancement – Adding some new features into
the existing software

Analysis and Design of IS 32

Popular SDLC Models
• Waterfall model: a sequential model that divides software
development into pre-defined phases. Each phase must be
completed before the next phase can begin with no overlap
between the phases.
 Each phase is designed for performing specific activity during the SDLC
phase.

Analysis and Design of IS 33

• Incremental Model: Incremental Model is one of the
most adopted models of software development process
where the software requirement is broken down into many
standalone modules in the software development life
cycle.

Analysis and Design of IS 34

• V-Model: a highly disciplined SDLC model which has a
testing phase parallel to each development phase.
 The V model is an extension of the waterfall model wherein
software development and testing is executed in a sequential way.
 It is known as the Validation or Verification Model.

Analysis and Design of IS 35

• Spiral Model: a risk-driven software development process
model. It is a combination of waterfall model and iterative
model.
 Helps to adopt software development elements of multiple process models
for the software project based on unique risk patterns ensuring efficient
development process.

Analysis and Design of IS 36

Summary
• The Software Development Life Cycle (SDLC) is a systematic process
for building software that ensures the quality and correctness of the
software built
• The full form SDLC is Software Development Life Cycle or Systems
Development Life Cycle.
• SDLC in software engineering provides a framework for a standard set
of activities and deliverables
• Seven different SDLC stages are
 1) Requirement collection and analysis
 2) Feasibility study
 3) Design
 4) Coding
 5) Testing
 6) Installation/Deployment
 7) Maintenance

Analysis and Design of IS 37

Summary
• The senior team members conduct the requirement
analysis phase
• Feasibility Study stage includes everything which should
be designed and developed during the project life cycle
• In the Design phase, the system and software design
documents are prepared as per the requirement
specification document
• In the coding phase, developers start build the entire
system by writing code using the chosen programming
language
• Testing is the next phase which is conducted to verify that
the entire application works according to the customer
requirement.

Analysis and Design of IS 38

Summary
• Installation and deployment face begins when
the software testing phase is over, and no bugs
or errors left in the system
• Bug fixing, upgrade, and engagement actions
covered in the maintenance face
• Waterfall, Incremental, Agile, V model, Spiral, Big
Bang are some of the popular SDLC models in
software engineering
• SDLC in software testing consists of a detailed
plan which explains how to plan, build, and
maintain specific software

Analysis and Design of IS 39

Alternatives to SDLC

• Computer Aided Software Engineering

(CASE) tools
• Prototyping
• Joint Application Development
• Rapid Application Development

Analysis and Design of IS 40

 • CASE Tools
•Upper Case Tools - Upper
CASE tools are used in
planning, analysis and design
stages of SDLC.
•Lower Case Tools - Lower
CASE tools are used in
implementation, testing and
maintenance.
•Integrated Case Tools -
Integrated CASE tools are
helpful in all the stages of
SDLC, from Requirement
gathering to Testing and
documentation.

Analysis and Design of IS 41

Types of CASE Tools:
• Diagramming Tools: represents system elements, control flow and
data flow among different software components and system structure
in a pictorial form.
Ex.: Flow Chart Maker tool for making state-of-the-art flowcharts.
• Computer Display and Report Generators:
understanding the data requirements and the relationships involved.
• Analysis Tools:
collecting requirements, automatically check for any irregularity,
imprecision in the diagrams, data redundancies or erroneous
omissions.
Ex.:
 (i) Accept 360, Accompa, CaseComplete for requirement analysis.
 (ii) Visible Analyst for total analysis.

Analysis and Design of IS 42

Types of CASE Tools:
• …
• Central Repository:
It provides the single point of storage for data diagrams, reports and
documents related to project management.
• Documentation Generators:
It helps in generating user and technical documentation as per
standards. It creates documents for technical users and end users.
Ex., Doxygen, DrExplain, Adobe RoboHelp for documentation.
• Code Generators:
It aids in the auto generation of code, including definitions, with the
help of the designs, documents and diagrams.

Analysis and Design of IS 43

• Traditional versus CASE systems
development life cycle

Analysis and Design of IS 44

• Prototyping

Analysis and Design of IS 45

 • Joint Application Development
(JAD)
 Structured process involving
users, analysts, and managers
 Several-day intensive workgroup
sessions
 Purpose: to specify or review
system requirements

Analysis and Design of IS 46

 • Rapid Application Development (RAD)
 Methodology to radically decrease design and
implementation time
 Involves: extensive user involvement, prototyping, JAD
sessions, integrated CASE tools, and code generators

Analysis and Design of IS 47

Câu hỏi

• Trình bày 7 giai đoạn của phương pháp

SDLC
• Chọn 2 mô hình để trình bày chi tiết. Điểm
mạnh yếu của mô hình.
• Giải thích phương pháp RAD

Analysis and Design of IS 48

Analysis and Design of IS 49