MODULE 2

Unit 07: Systems Development Life Cycle

The aim of an SDLC methodology is to give IT Project Managers the tools they
need to assure the effective deployment of systems that meet the University's
strategic and business goals.

ROLE IN THE PROJECT PROPOSAL

System Analyst
● A systems analyst investigates, analyzes, designs, develops, installs,
evaluates, and maintains a company’s information systems.
● On large projects, the analyst works as a member of an IT department
team
● Smaller companies often use consultants to perform the work

SYSTEM DEVELOPMENT

System development is the process of defining, designing, testing and

implementing a software application. A system development project includes a
number of different phases, such as feasibility analysis, requirements analysis,
software design, software coding, testing and debugging, installation and
maintenance.

System Development Methods

Systems Development Life Cycle
● Predictive Approach
● Use of Process Models
● Process-centered technique

Page | 1
System Development Life Cycle(SDLC)

Systems Planning – It is the initial stage in the systems development life cycle
(SDLC). It is the fundamental process of understanding why an information
system should be built and determine how the project team will go about building
it. It describes how IT projects get started, how systems analysts evaluate
proposed projects, the feasibility of a project, and the reasoning behind the
proposed system development.

Systems Analysis – System analysts must do analysis activities when creating

a new system or improving an old system. If an information system is built
properly, it will give the expected benefits to the company. To achieve this goal,
system analysts define what the information system requires by performing the
analysis activities.

Page | 2
Systems Analysis Activities

The systems analysis phase consists of requirements modeling, and process

modeling, object modeling, and consideration of development strategies.

Watch the Lesson 07 Requirements.mp4 video.

Requirements Modeling
● Describes requirements modeling, which involves fact-finding to
describe the current system and identification of the requirements
for the new system. These requirements are:
▪ Inputs refer to necessary data that enters the system, either
manually or in an automated manner.
▪ Processes refer to system characteristics such as speed,
volume, capacity, availability, and reliability.
▪ Outputs refer to electronic or printed information produced by
the system.
▪ Performance refers to the logical rules that are applied to
transform the data into meaningful information.

Page | 3
 ▪ Security refers to hardware, software, and procedural
controls that safeguard and protect the system and its data
from internal or external threats.

Watch the IPO video: Lesson 07 Video 02 IPO.mp4

Flowchart
● Business flowchart shows the steps that make up a business
process, along with who's responsible for each step.
● They are useful for analyzing current processes, planning
improvements, and crystallizing communication between process
participants

Types of Flowchart:
● Document
• Illustrates the flow of documents and information
between areas of responsibility within an organization.
• A document flowchart is particularly useful in analyzing
the adequacy of control procedures.

Page | 4
 ● System
▪ System flowcharts depict the relationship among the input,
processing, and output of an AIS
● Program
▪ A program flowchart describes the specific logic to perform a
process shown on a systems flowchart

Check the following videos for further discussion on the Flowcharting process.
• Lesson 08 FlowCharting.mp4
• Flowchart Tutorial (with Symbols, Guide and Examples)

System Requirements
In the context of software development and system design, requirements are
statements that describe what the system should do or possess to meet the
needs of its users and stakeholders. These requirements can be broadly
categorized into two types: functional requirements and nonfunctional
requirements.

Examples of functional requirements for a website:

● Allow users to register and log in to their accounts.
● Provide a search functionality to find products or information.
● Enable users to add items to a shopping cart and proceed to checkout.
● Allow administrators to manage user accounts and product listings.
● Display real-time stock availability for products.

Non-functional Requirements:
Non-functional requirements, on the other hand, define the attributes and
qualities that describe how the system should perform, rather than what it should
do. These requirements focus on aspects related to system behavior,
performance, security, and user experience. Nonfunctional requirements
answer the question, "How well does the system perform?"

Examples of non-functional requirements for a website:

● Performance: The website should load within 3 seconds to provide a
good user experience.

Page | 5
 ● Scalability: The system should handle an increasing number of users
without significant performance degradation.
● Security: User passwords should be securely hashed and stored to
prevent unauthorized access.
● Usability: The website's interface should be intuitive and easy to navigate
for users of all experience levels.
● Reliability: The system should have at least 99.9% uptime, with minimal
downtime for maintenance.

It's important to note that both functional and non-functional requirements are
crucial for successful system development. Functional requirements define
what the system should achieve in terms of features and capabilities, while non-
functional requirements ensure the system meets the desired levels of
performance, quality, and user satisfaction. Both sets of requirements play a
key role in guiding the design, development, testing, and validation of the
system.

Systems Design – Systems Design is the third of five phases in the systems
development life cycle (SDLC). Now you are ready to begin the physical design
of the system that will meet the specifications described in the system
requirements document. Systems design tasks include output and user
interface design, data design, and system architecture.
A video by Johnny Khoury has explained how the Design Phase in SDLC
(Lesson07 video01 Design Phase in SDLC) works. It is all about the design
phase of creating a system.

System Design Guidelines:

The systems analyst must understand the logical design of the system before
beginning the physical design of any one component
● Data design
● User interface
● Architecture
● System design specification

Page | 6
System Design Objectives
The goal of systems design is to build a system that is effective, reliable, and
maintainable
● A system is effective if it meets all user needs and business requirements
● A system is reliable if it adequately handles errors
● A system is maintainable if it is well designed, flexible, and developed
with future modifications in mind

System Design Considerations

● User Considerations
▪ Carefully consider any point where users receive output from, or
provide input to, the system
▪ Anticipate future needs of the users, the system, and the
organization – hard-coded
▪ Provide flexibility
▪ Parameter, default

● Data Considerations
▪ Data should be entered into the system where and when it occurs
because delays cause data errors
▪ Data should be verified when it is entered, to catch errors
immediately
▪ Automated methods of data entry should be used whenever
possible
▪ Audit trail
▪ Every instance of entry and change to data should be logged
▪ Data should be entered into a system only once
▪ Data duplication should be avoided

● Design Trade-Offs
▪ Most design trade-off decisions that you will face come down to
the basic conflict of quality versus cost
▪ Avoid decisions that achieve short-term savings but might mean
higher costs later

Prototyping

Page | 7
 The method by which a prototype is developed. It involves a repetitive
sequence of analysis, design, modeling, and testing. It is a common technique
that can be used to design anything from a new home to a computer network.

Prototyping Methods
● System prototyping - produces a full-featured, working model of the
information system. Because the model is “on track” for implementation,
it is especially important to obtain user feedback, and to be sure that the
prototype meets all requirements of users and management.
● Design prototyping or Throwaway prototyping – method of development
that employs technical mechanisms for reducing risk in a project, when
the project needs are vaguely and poorly laid out. The end product of
design prototyping is a user-approved model that documents and
benchmarks the features of the finished system.
● Prototyping offers many benefits
▪ Users and systems developers can avoid
misunderstandings
▪ Managers can evaluate a working model more effectively
than a paper specification ● Consider potential problems
▪ The rapid pace of development can create quality problems
▪ In very complex systems, the prototype becomes unwieldy
and difficult to manage

Prototyping Tools – systems analysts can use powerful tools to develop

prototypes
● CASE tools - Computer-aided systems engineering (CASE), also called
computer-aided software engineering, is a technique that uses powerful
software, called CASE tool, to help systems analysts develop and
maintain information systems.
● Application generators -A tool that supports the rapid development of
computer programs by translating a logical model directly into code. Also
called a code generator.
● Report generators - a computer program whose purpose is to take data
from a source such as a database, XML stream or a spreadsheet, and

Page | 8
 use it to produce a document in a format which satisfies a particular
human readership
● Screen generators - or form painter, is an interactive tool that helps you
design a custom interface, create screens forms, and handle data entry
format and procedures.

Limitations of Prototypes
● A prototype is a functioning system, but it is less efficient than a fully
developed system
● Systems developers can upgrade the prototype into the final information
system by adding the necessary capability. Otherwise, the prototype is
discarded

Future Trends in Software Development

Many software development tools and technologies are in transition
● Web services
● Open source software
● Service-oriented architecture (SOA)
● Loose coupling
● Software quality is more important than ever

Here are some links on how to create prototypes:

● Create interactive prototypes with MS PowerPoint
● Pencil Project | Free UI Mockup Design Software
● Prototyping Tool for Mobile and Websites
● Build a WIX Website For FREE in 10 Minutes

Page | 9
User Interface
Describes how users interact with a computer system, and consists of all
the hardware, software, screens, menus, functions, output, and features that
affect two-way communications between the user and the computer.
Graphical User Interface - uses visual objects and techniques that allow users
to communicate effectively with the system.
Usability – user satisfaction, support for business functions, and system
effectiveness
● Process-control systems – allow users to send commands to the system
● User-centered systems – how users communicate with the information
system, and how the system supports the firm’s business operations
User interface requires the understanding of human-computer interactions and
user-centered design principles.
Human-Computer Interaction describes the relationship between computers
and people who use them to perform their jobs

Page | 10
Seven Habits of Successful Interface Designers:
1. Understand the Business
The interface designer must understand the underlying business
functions and how the system supports individual, departmental, and
enterprise goals. The overall objective is to design an interface that helps
users to perform their jobs.

2. Maximize Graphical Effectiveness

Studies show that people learn better visually. The immense popularity of
Apple’s iOS and Microsoft Windows is largely the result of their GUIs that
are easy to learn and use. A well-designed interface can help users learn a
new system rapidly and be more productive.

3. Think Like a User

The designer must learn to think like a user and see the system through
a user’s eyes. The interface should use terms and metaphors that are
familiar to users. Users are likely to have real-world experience with many
other machines and devices that provide feedback, such as automobiles,
ATMs, and microwave ovens. Based on that experience, users will expect
useful, understandable feedback from a computer system.

4. Use Models and Prototypes

From a user’s viewpoint, the interface is the most critical part of the system
design because it is where he or she interacts with the system — perhaps
for many hours each day. It is essential to construct models and prototypes
for user approval. An interface designer should obtain as much feedback as
possible, as early as possible.

5. Focus on Usability
The user interface should include all tasks, commands, and
communications between users and the information system. The opening
screen should show the main option. Each screen option leads to another
screen, with more options.

6. Invite Feedback
Even after the system is operational, it is important to monitor system
usage and solicit user suggestions. The analyst can determine if system
features are being used as intended by observing and surveying users.

Page | 11
7. Document Everything
All screen designs should be documented for later use by programmers.

Systems Implementation – This phase begins once the client has tested and
approved the system. The system is installed at this phase to support the
specified business functions. The performance of the system is compared to the
performance targets defined during the planning phase.
Systems Maintenance – System maintenance is a continuous operation that
includes eliminating program and design flaws, updating documentation and
test data, and updating user support.

Page | 12