Software Development Life Cycle (SDLC) and System Analysis Process

COVER PAGE

Contents
1 Introduction..............................................................................................................................................3
2 Software Development Life Cycle (SDLC)..................................................................................................3
2.1 Requirements gathering and analysis................................................................................................4
2.2 Design................................................................................................................................................4
2.3 Implementation and coding...............................................................................................................5
2.4 Testing...............................................................................................................................................5
2.4 Deployment.......................................................................................................................................6
2.5 Maintenance......................................................................................................................................6
3 Class diagram............................................................................................................................................7
3.1 Membership system..........................................................................................................................7
3.2 Facility management System.............................................................................................................8
4 Use case diagrams....................................................................................................................................9
4.2 use case to model actors and use cases of the manager schedules staff roaster..............................9
4.2 Membership registration system.....................................................................................................10
5 PERT/CPM...............................................................................................................................................11
References.................................................................................................................................................13

1 Introduction
This report discusses the system analysis process of the Body Sculptors gymnasium which is currently
using a computer-based information system to monitor and track membership and member activities in
the gymnasium. The report discusses how the six core process of the software development life cycle
(SDLC) are applicable in the development of the proposed system. To model the system, UML diagrams
are used.
2 Software Development Life Cycle (SDLC)
SDLC can be defined as a framework that defines or specifies steps that are followed while developing a
software. SDLC covers on the details of the plan for building, deploying and performing maintenance on
a software. Following all stages of the SDLC helps achieve a systematic process of developing the
software. SDLC was developed with the main goal being to develop a high quality at the end of the
process. The following are the 6 stages of the SDLC;
 Requirements gathering and analysis
 Design
 Implementation and coding
 Testing
 Deployment
 Maintenance
The diagram shows the representation of the stages making up the SDLC;
Figure 1: Diagramatic representation of the stages of SDLC

2.1 Requirements gathering and analysis
This is the first phase of the software development life cycle. At this stage of the process, requirements
of the system being developed are collected and analyzed. Collection of requirements is done through a
process called requirements engineering where the project manager together with the project team
organize meetings with the customer to gather all information about the system. There are various
methods that are used for requirements gathering but perhaps the most common and the most
applicable for the proposed Body Sculptors gymnasium information system are;
 Case study review- This method of requirements gathering involves analyzing the case study
with the details of the business operation. The requirements gathering team goes through the
case study analyzing all information and presents its finding it terms of requirements to the
project manager.
 Interviews- conduction of interviews is another efficient and costly method of requirements
gathering. Interviews are conducted to the customer of the business. The interviews can involve
one or more employees working in the organization to get their view of how the system is
supposed to help them and this is analyzed to come up with a set of requirements. There are
three types of interviews; structured interviews, unstructured interviews and semi-structured
interviews. Structured interviews follows a specific structure where by the interviewer follows a
set of questions which are answered by the interviewee and both parties are not supposed to
deviate from the set of questions. Unstructured interviews do not follow any structure and the
interviewer does not necessarily need to have interview questions. The interview is open and
both parties can deviate as much as they want. Semi-structured is a combination of structured
and unstructured interviews. In semi-structured interviews, the interviewer follows a set of
questions but both parties are allowed to deviate from the list of interview questions. Semi-
structured interviews are the best especially for the recommended system because they will
make analysis of the results easy as well as help gather all possible requirements from the
interviewees.
 Observation- Observation is one of the cheapest requirements gathering technique. This can be
done by sending the requirements gathering team to the business premises of the customer
where they are supposed to engage themselves in the day to day running of the business while
at the same time gathering requirements on the business operations.
The recommended technique for the proposed system is using a combination of the three techniques
because this will ensure that all requirements are gathered and there exists no doubt between the
customer and the project team. After the requirements are collected, they are analyzed by the project
team and a software requirements specification document is produced.
2.2 Design
This is the next stage in the SDLC after requirements gathering and analysis. This stage uses the software
specifications document achieved in the previous state. The document is analyzed and used to define
the architecture of the system. Common techniques that are used in this stage of the SDLC include use
of wireframes to define the design of the system. UML diagrams are also to model the design of the
system (Nishadha, 2015). Story boards are also used to illustrate how the design meets the functional
requirements of the customer. At the end of this stage, a software design document (SDD) is produced.