Ask a question from expert

Ask now

System Analysis & Design : Software Development Life Cycle

46 Pages10454 Words242 Views
   

Added on  2022-01-19

System Analysis & Design : Software Development Life Cycle

   Added on 2022-01-19

BookmarkShareRelated Documents
System Analysis & Design
Pearson BTEC Level 4 & 5 HND/HNC
In Computing
Abdul Rafeh
System Analysis & Design :  Software Development Life Cycle_1
Contents
Introduction...........................................................................................................................................4
Software Development Life Cycle (SDLC)...........................................................................................5
P1 Discuss the strengths and weaknesses of the traditional and agile systems analysis
methodologies.......................................................................................................................................6
Traditional SDLC..................................................................................................................................6
WaterFall Model................................................................................................................................6
Prototyping Model.............................................................................................................................7
Spiral Model......................................................................................................................................8
Agile Methodologies.............................................................................................................................9
Scrum................................................................................................................................................9
Extreme Model................................................................................................................................11
Lean.................................................................................................................................................12
Scaled Agile Framework.................................................................................................................14
Disciplined Agile Delivery..............................................................................................................16
Kanban............................................................................................................................................19
Agile Modelling..................................................................................................................................21
Dynamic System Development Method (DSDM)...........................................................................21
Feature-Driven Development..........................................................................................................23
Conclusion.......................................................................................................................................25
P2 Produce a feasibility study for a system for a business related problem........................................26
System investigation of given scenario................................................................................................26
Feasibility Report................................................................................................................................26
Technical feasibility........................................................................................................................26
Economic feasibility........................................................................................................................26
Legal feasibility...............................................................................................................................27
System Analysis & Design :  Software Development Life Cycle_2
Operational feasibility.....................................................................................................................27
Vision and Goals of the project...........................................................................................................27
Cost/Benefit analysis...........................................................................................................................27
Legal analysis......................................................................................................................................28
Timeframe of the project.....................................................................................................................28
Cultural Security Considerations.........................................................................................................29
Organisational Culture.....................................................................................................................29
P3 Analyses a system using a suitable methodology for a business-related problem.........................29
Methodology.......................................................................................................................................29
Feasibility study.......................................................................................................................29
Business study.........................................................................................................................29
Design and Build......................................................................................................................30
Implementation.......................................................................................................................30
User and System requirements............................................................................................................30
Constraints...........................................................................................................................................30
Roles and Responsibilities...................................................................................................................31
Project Manager...............................................................................................................................31
Team Member.................................................................................................................................31
Business Analyst.............................................................................................................................32
Project Stakeholders........................................................................................................................32
Project Documentation........................................................................................................................32
Documentation Stages.....................................................................................................................33
P4 Design a fully functional system to meet user and system requirements for the business related
problem...............................................................................................................................................34
Data Flow Diagram.............................................................................................................................34
Flow Chart...........................................................................................................................................35
Entity Relation Diagram......................................................................................................................36
Function...............................................................................................................................................37
User login........................................................................................................................................37
Search inventory..............................................................................................................................37
Add product.....................................................................................................................................38
Add item..........................................................................................................................................38
Purchase item..................................................................................................................................38
Sales................................................................................................................................................38
System Analysis & Design :  Software Development Life Cycle_3
Billing..............................................................................................................................................38
Tools and Techniquesy........................................................................................................................39
Database Applications.....................................................................................................................39
Tools................................................................................................................................................39
Techniques......................................................................................................................................40
Web Applications............................................................................................................................40
Tools................................................................................................................................................40
Techniques......................................................................................................................................41
Software Application.......................................................................................................................41
Tools................................................................................................................................................41
Techniques......................................................................................................................................42
Design Documentation........................................................................................................................42
Software Design Documentation.....................................................................................................43
Web Design Documentation............................................................................................................43
Database Design Documentation.....................................................................................................44
References...........................................................................................................................................44
Introduction
The following paper is about different aspect related to system analysis and design. I have
been given a task to carry out a project for Suzuki parts manufacturing company. For this I
have to do following several things.
Initially, I have to study about different types of development methodologies that may be
traditional or agile.
Secondly, I have to choose the best methodology in order to develop a new agile type of
system for Suzuki parts manufacturing company using which they can easily collect orders
and maintain information.
After that, I have to do feasibility study on whether the chosen methodology suits my
purpose and whether it is economically feasible.
Fourthly, I will assemble a team of developers and business analyst to deal with different
aspect of the project.
System Analysis & Design :  Software Development Life Cycle_4
Finally, I will deliver the developed system to Suzuki parts manufacturing company and
teach their employees on how to use the new system.
Software Development Life Cycle (SDLC)
Software Development Life Cycle is a process used in software industry to design, develop,
implement, maintain and test softwares. The main aim of SDLC is to produce high quality
software that meets or exceeds customers’ expectation, reaches completion within cost and
time estimates.
SDLC stands for Software Development Life Cycle
Also known as Software Development Process
It is a frameworks that defines task performed at each step in the software
development process
ISO/IEC 12207 is the international standard for software life-cycle processes.
Software Development Life Cycle works of the basic principle of lowering the cost of
software development and at the same time improving quality and shortening the production
time. A picture below describes the basic steps in any type of SDLC:
System Analysis & Design :  Software Development Life Cycle_5
P1 Discuss the strengths and weaknesses of the traditional and agile
systems analysis methodologies.
Traditional SDLC
WaterFall Model
The first SDLC process ever introduced was WaterFall Model. It is very simple to understand
and use. In WaterFall Model, each phase must be completed before subsequent phase can
begin and there's no overlapping within the phases.
It works on simple principle where outcome of first phase acts as the input for the next phase
sequentially. That means, if the previous phase is not completed and signed off the next phase
cannot begin. It is sequential design process in which progress is seen steadily flowing
downwards. It can also be referred to as Linear-Sequential Life Cycle Model as the
development process is in a linear sequential flow.
The picture below illustrates the working design of WaterFall Model:
System Analysis & Design :  Software Development Life Cycle_6
Strengths Weaknesses
It allows departmentalization and control. A
schedule can be set with deadlines for each
stage of development
Estimation of time and cost for each phase is
difficult in this model
It progresses through easily understandable
and explainable phases
It is very difficult to go back and change
something once the application is in testing
stage
It is easy to manage as it is very rigid. It is not a useable model for complex and
object oriented projects
It works well for smaller projects where
requirements are very well understood
Not suitable for a project where requirements
are at moderate to high risk of changing
Prototyping Model
An early sample, model or release of a product built to test a concept is called Prototyping
Model. It is used to provide specifications for a real, working system rather than a theoretical
one.
It works on a principle that instead of freezing the requirements before a design or coding, a
throwaway prototype is built to better understand the requirements. The prototype is based on
early understanding of the requirements. It helps the clients to better understand the
requirements of the desired system. Prototyping is very helpful idea for complicated and large
systems for which there is no manual process or existing system to help determining the
requirements.
The picture below shows the life-cycle of prototyping model:
System Analysis & Design :  Software Development Life Cycle_7
Strengths Weaknesses
Prototyping demonstrates the concept to
prospective investors in order to get the
funding
It disturbs the rhythm of development team if
too many changes are required
Potential risks can be identified early and
corrective steps can be taken
Prototyping may increase the complexity of
the system as scope may expand beyond
original plans
The user/client gets a better understanding of
the system being developed and can suggest
changes/modifications
It is usually done at the cost of the developer.
Spiral Model
A combination of Iterative Development Model and WaterFall Model is known as Spiral
Model. It has very high emphasis on risk analysis. It allows for additional releases of the
product through each iteration around the spiral.
It is best used for large projects that need continuous enhancements. Specific activities are
needed to be done in one spiral where the output is a small prototype of large software. The
picture below shows a basic working of Spiral Model:
Strengths Weaknesses
Cost estimation is easy as prototype building
is done in small parts
It works best only for large projects and is
very expensive for small projects
Development can be divided into smaller
parts and more risky parts can be developed
Requires experts people for risk assessment
as risk analysis is the most important phase
System Analysis & Design :  Software Development Life Cycle_8

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
System Development Life Cycle (SDLC) - A Survey
|47
|18551
|217

ISTM 6201 Information Systems Development Assignment
|49
|5662
|73

Design and Development of Quadcopter for Advanced Manufacturing-II
|42
|11891
|479

Project Integration Management
|47
|9786
|398

Midterm Exam Week 4
|14
|1404
|267

Software Development Lifecycles PDF
|107
|33743
|261