Membership and Facility Management System Analysis and Design

This project details the system analysis and design of a Membership and Facility Management System (MFMS) for a gymnasium, encompassing the Software Development Life Cycle (SDLC) processes. The assignment begins by discussing the six core processes of the SDLC, emphasizing their importance in disciplined software development. It then presents a comprehensive class diagram illustrating the system's attributes, methods, relationships, and multiplicities. Use case diagrams are provided to model the actors and use cases for both the manager, focusing on staff roster scheduling, and the member, specifically the registration process. Finally, a PERT/CPM chart is developed to analyze the project timeline, identifying the critical path and the total project duration. The project aims to provide a structured approach to developing a high-quality software product for managing gymnasium operations, ensuring efficient membership and facility management. The student has made assumptions and clearly stated them.

Running head: SYSTEM ANALYSIS AND DESIGN OF A MFMS
System Analysis and Design of a Membership and Facility Management System (MFMS)
Name of the Student
Name of the University
Author note

1SYSTEM ANALYSIS AND DESIGN OF A MFMS
Table of Contents
1. Six Core Processes of the SDLC for the Membership and Facility Management System..........2
2. Class Diagram for the entire membership and facility management system...............................9
3. Use case diagram modelling actors and the use cases of the Manager Schedules staff roster. .10
4. Use case diagram modelling the actors and the use cases of the Member registers..................11
5. PERT/CPM chart.......................................................................................................................12
References......................................................................................................................................13

2SYSTEM ANALYSIS AND DESIGN OF A MFMS
1. Six Core Processes of the SDLC for the Membership and Facility Management System
The software development life cycle (SDLC) models provides a certain definition of
certain phases present within the cycle of software development. This also discusses the ways in
which these phases would be executed. Every kind of processes that are performed within the
phase of developing a software would require a proper kind of analysis and planning, which
would help in constructing the base of the plan for software development plan (Rastogi 2015).
The different models within the software development life cycle (SDLC) discusses the ways in
which a proper kind of approach should be developed for preparing the software development
plan and execute them accordingly.
Each of the phases present within the SDLC helps in producing some form of clear
deliverables that would be highly required within the next phase of the software life cycle.
During each phase of the SDLC, the defined requirements would be translated to produce some
kind of design that would help in developing a proper software product. The code that is
produced and written during the development phase of the product is prepared according to the
discussed design, which is also known as the development phase (Velmourougan et al. 2014).
After the coding of the software platform has been made, the testing phase is put forward that
verifies the software product according to the pre-listed deliverables. The Testing Team deeply
follows the Software Testing Life Cycle (STLC) that is similar to the cycle of development that
is mainly followed by the Development Team.
The discussion in this report puts focus over the developmental aspect of a Membership
and Facility Management System (MFMS). This system would be made use by Body Sculptors
Gymnasium in order to manage each of the aspects of work that are performed within the gym.

3SYSTEM ANALYSIS AND DESIGN OF A MFMS
This system would maintain the membership of each of the members within the gymnasium. The
software system would also make use of intelligent systems that would help in preparing of
rosters for each of the members. This would help in the management of facilities that are
provided and are accessed by the members. The completed developed system would prove to be
hugely helpful for the members in organising their daily routine activities (Ali 2017). However,
in order to design the software product, the software development team would need to follow the
six important processes as described within the SDLC model of software development. Adhering
with the different processes of SDLC would lead towards the proper process of developing of
software in a disciplined and systematic manner.
The main purpose of incurring the process of SDLC models within the development of
the MFMS is to deliver a high quality within the software product and as per the requirement of
the customer. The different defined phases within the SDLC are discussed as: Gathering of
Requirement and performing analysis, designing the code and planning for the progress, coding
of the software model, rigorous testing of the developed software, deployment of the product and
future maintenance over the product.
The different phases of the SDLC that would be followed during the development of the
MFMS are discussed in the following steps –
1. Gathering of Requirement and Analysis – This is defined as the initial phase within
the phase of developing of the software product. In this phase, each of the relevant information
would be collected from the customer. This information that would be gathered would be highly
critical in nature in order to be understood and properly developed in order to satisfy the
expectation of the customer (Alshamrani and Bahattab 2015). Any form of ambiguities within
the understanding of the customer requirements should be resolved at this phase.

4SYSTEM ANALYSIS AND DESIGN OF A MFMS
In this phase, the administration staff, managers and project manager would form a
meeting. The main objective of the meeting would be to discuss about interviewing the
administration staff and manager and thus understanding exact requirements. The project
manager would gather the information in order to understand the expectation of the customer
from the software product. In this case, the main requirement of the administration of Body
Sculptor Gymnasium would be to develop a system that would be highly helpful in the
maintaining a track of their members, the membership facilities and various other facilities that
are provided to them.
The purpose of the software product would also be need to be determined in this phase.
Hence, before the building of such a software product, a proper understanding about the product
would be highly important. After the requirement has been gathered, the project manager would
perform a brief analysis over the requirements would be done. During the analysis of the reports,
any kind of ambiguity if found would be reported and thus further discussion would be
proceeded accordingly.
After every kind of requirement have been clearly understood, the project manager would
work closely with the development team in order to design a Software Requirement
Specification (SRS) document. This document should be prepared in order to discuss each of the
next phases of the development of the software product (Aljawarneh, Alawneh and Jaradat
2017). The document would act as a guide for the software developers. This guide should also be
reviewed by the acting customers for any form of future reference.
2. Design of the System – During the second phase of the SDLC model, the necessary
specifications, operations and features that would be helpful for sustaining the functional
requirements of the to-be designed system would be put in action. The use of system design

5SYSTEM ANALYSIS AND DESIGN OF A MFMS
would help in the identification of requirements for the system and hardware. It further the
providing a definition of the computing architecture of the system (Davis and Yen 2018). The
networking capabilities, procedures and processing power would also be need to be determined
in this phase of the SDLC. The specifications provided within the system design also helps in
serving as a certain form of input based on producing the next phase of the software model.
3. Coding or Implementation – This phase mostly begins after the development team
would receive the design document. In this phase, the design of the software that had been
proposed within the second phase of the SDLC would be put in proper action (Roy, Dasgupta
and Chaki 2016). Each of the necessary components that need to be implemented within the new
software product would be incorporated in this phase of the software development.
Upon receiving the documents based on system design, the designers and other
concerned teams would work together. During this phase, the team for software development
would divide each of the modules into several parts that would help in easing the process of
developing the software. Since, this phase is in relation with the development of the software
product, hence the primary form of focus would be put over the developers (YANG and Bi
2014). This part is thus considered as the longest phase within the SDLC model. In particular,
the software programmers, database engineer and network engineer would work in unison to
develop each of the parts that need to be included within the software product. A flowchart might
be prepared in order to ensure that each of the phases of the development would be performed in
an organized manner.
With the completion of the coding phase, it would mark the end of the primary section of
the software development process. In an additional form, this phase would mark the starting of

6SYSTEM ANALYSIS AND DESIGN OF A MFMS
the production phase (Dora and Dubey 2015). During this phase, a proper form of focus over the
training aspects could be considered as highly beneficial during the phase.
4. Testing Phase – After the coding phase of the project would be completed, it would be
the responsibility of testing team to come together and perform high level tests over the defined
software. The software that would be developed for the gymnasium would comprise of several
modules (Yadav and Yadav 2015). Hence, the testing team would form a plan for testing each of
the included modules within the system. During this phase, the developed software would be
tested in a thorough manner.
After the development of the software product, it would be passed to the testing team.
The professionals within the testing team would ensure that each of the needs would be
addressed and thus they have been met as per the gathered requirements in the initial phase. All
forms of testing that have been defined in the testing phase that includes integration testing, unit
testing, acceptance testing and system testing would be done along with the non-functional form
of testing.
During this phase, each of the modules would be tested in a proper manner. Regression
testing and retesting would be performed again and again till the point to which the software
would be developed as per meeting with the expectation of the customers (Khan and Khan
2014). The testers within the team would make use of the SRS document in order to ensure that
the software would have been developed as per the standard set by the customer.
5. Deployment Phase – The deployment phase marks the final phase within the SDLC
model of developing the software product. After this phase, the software product is put into the
production phase. The entire project team performs rigorous form of testing over the software

7SYSTEM ANALYSIS AND DESIGN OF A MFMS
product. The product passes through every kind of testing and then the project team puts a final
approval over the software being developed (Virmani 2015). After the final approval from the
project team, the product would be made live to the users. Under the phase of the product
deployment, the project development team would help the administrative staff within the
gymnasium to prepare for the installation of the software. It would also conduct another kind of
test after the proper form of implementation of the designed software.
After the installation phase would be complete, the team involved within the project
would create different kind of procedures based on operations. The operating procedures would
help the project team in preparing them according to the instructions based on gaining
information about the working procedure of the software (Geogy and Dharani 2015). The
administrative staff within the gymnasium should also decide on the factors that were the
primary criteria of operations. In this step, any kind of issues if present within the software
product would be detected and updated as soon as possible.
6. Maintenance Phase – The Maintenance phase within the design of the membership
and facility management system would begin only after the proper form of deployment phase
and when the software would be fully operational. This phase, thus includes the implementation
of certain form of changes that would be required when the software would be fully functional
(Mateen and Akbar 2016). The implementation of new form of requirements within the software
application would be mainly deployed at the location of the customer.
The phase of maintenance over the software product would also include the handling of
the residual kind of errors that would exist within the software after performing of rigorous
testing over the software. The maintenance phase within the SDLC discuss the aspects of

8SYSTEM ANALYSIS AND DESIGN OF A MFMS
performing maintenance over the software product, rectification of bugs if detected within the
system and also process the number of changes that would be required.
The maintenance phase, which is also sometimes termed as support, can be defined as a
crucial form of activity based on linking the experience of the customers and maintain the
delivery of the product across the organization (Malhotra and Chug 2016). The most important
form of deliverables that would be discussed within the key deliverables are: the system would
be kept live during the process of usage, the code would be maintained on a regular basis and
any form of update over the software as and when required. The process of maintenance within
the software product happens during the post-deployment phase of the software. Any form of
changes, additions, correction would move to a certain computing platform. The development
team should be able to establish certain standards based on change management based on making
modifications and ensuring that these modifications would not disrupt the phase of operations. It
should also be ensured that the performance or security of the system would be maintained
(Sharma 2017). The administrative staff should also maintain that management would be able to
establish some form of change controls that would ensure modifications over the software and
ensure patches to the software.

9SYSTEM ANALYSIS AND DESIGN OF A MFMS
2. Class Diagram for the entire membership and facility management system
(Figure 1: Class Diagram for the Software System)
(Source: Created by author)

10SYSTEM ANALYSIS AND DESIGN OF A MFMS
3. Use case diagram modelling actors and the use cases of the Manager Schedules staff roster
(Figure 2: Use Case Diagram for the staff roster)
(Source: Created by author)

11SYSTEM ANALYSIS AND DESIGN OF A MFMS
4. Use case diagram modelling the actors and the use cases of the Member registers
(Figure 3: Use Case Diagram for the Member registers)
(Source: Created by author)

12SYSTEM ANALYSIS AND DESIGN OF A MFMS
5. PERT/CPM chart
(Figure 4: PERT/CPM chart)
(Source: Created by author)
The total time taken for the project is 92 days. However, the parts highlighted in red are defined as critical path activities.

13SYSTEM ANALYSIS AND DESIGN OF A MFMS
References
Ali, K., 2017. A Study of Software Development Life Cycle Process Models. International
Journal of Advanced Research in Computer Science, 8(1).
Aljawarneh, S.A., Alawneh, A. and Jaradat, R., 2017. Cloud security engineering: Early stages
of SDLC. Future Generation Computer Systems, 74, pp.385-392.
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Davis, W.S. and Yen, D.C., 2018. The information system consultant's handbook: Systems
analysis and design. CRC press.
Dora, S.K. and Dubey, P., 2015. Software Development Life Cycle (SDLC) Analytical
Comparison and Survey on Traditional and Agile Methodology. National Monthly Referred
Journal of Research Science and Technology, 2(8).
Geogy, M. and Dharani, A., 2015, February. Prominence of each phase in Software development
life cycle contributes to the overall quality of a product. In 2015 International Conference on
Soft-Computing and Networks Security (ICSNS) (pp. 1-2). IEEE.
Khan, M.E. and Khan, F., 2014. Importance of software testing in software development life
cycle. International Journal of Computer Science Issues (IJCSI), 11(2), p.120.
Malhotra, R. and Chug, A., 2016, March. Comparative analysis of agile methods and iterative
enhancement model in assessment of software maintenance. In 2016 3rd International

14SYSTEM ANALYSIS AND DESIGN OF A MFMS
Conference on Computing for Sustainable Global Development (INDIACom) (pp. 1271-1276).
IEEE.
Mateen, A. and Akbar, M.A., 2016. Estimating software reliability in maintenance phase through
ann and statistics. arXiv preprint arXiv:1605.00774.
Rastogi, V., 2015. Software development life cycle models-comparison,
consequences. International Journal of Computer Science and Information Technologies, 6(1),
pp.168-172.
Roy, B., Dasgupta, R. and Chaki, N., 2016. A study on software risk management strategies and
mapping with SDLC. In Advanced Computing and Systems for Security (pp. 121-138). Springer,
New Delhi.
Sharma, M.K., 2017. A study of SDLC to develop well engineered software. International
Journal of Advanced Research in Computer Science, 8(3).
Velmourougan, S., Dhavachelvan, P., Baskaran, R. and Ravikumar, B., 2014, September.
Software development Life cycle model to build software applications with usability. In 2014
International Conference on Advances in Computing, Communications and Informatics
(ICACCI) (pp. 271-276). IEEE.
Virmani, M., 2015, May. Understanding DevOps & bridging the gap from continuous integration
to continuous delivery. In Fifth International Conference on the Innovative Computing
Technology (INTECH 2015) (pp. 78-82). IEEE.
Yadav, H.B. and Yadav, D.K., 2015. A fuzzy logic based approach for phase-wise software
defects prediction using software metrics. Information and Software Technology, 63, pp.44-57.

15SYSTEM ANALYSIS AND DESIGN OF A MFMS
YANG, L.Q. and Bi, Y.Y., 2014. Internet of things technology implementation by applying
SDLC model: The intelligent storage management system. In Applied Mechanics and
Materials (Vol. 556, pp. 5385-5390). Trans Tech Publications.