Software Development Processes for Allsports Sports Club

This paper discusses the software development processes for Allsports Sports Club, including the selection of a development methodology, requirement gathering techniques, and functional and non-functional requirements. It also includes sample questionnaires, class diagrams, use case diagrams, entity relationship diagrams, data flow diagrams, and activity diagrams.

System Analysis 1
Software Development Processes
By (Name)
The name of the Class (course)
Professor (Tutor)
The Name of the School (University)
The City and State where it is located
The Date

System Analysis 2
Software Development Processes
Section A: Requirement Analysis
1. Introduction
System development is a multi-phased approach through which software products are
realized. Irrespective of the approach used, requirements analysis and data modelling are done to
create a clear picture of the system that is being developed. This development start with selection
of a methodology that is informed on budget constraints, expertise, type and nature of system
being developed among other factors. The aim of this paper is to justify the selection of a
development methodology, requirement gathering techniques, elicit both non-functional and
non-functional requirements and a sample questionnaire for a system that is needed to streamline
services at the Allsports Sports Club (ASC).
2. Problem Justification
Currently, the syste being used by the club allows for limited number of members,
software options while some newsletters have been published late, contrary to the organization’s
principles. Difficulties experienced in generating reports plus increased membership have
created the need for a new system to streamline services at the club.
3. Software Development Methodology
Software development methodology refers to the set of rules or approach used in the
processes of requirements elicitation, planning, designing, implementation, installation and
maintenance of a new software product. It also includes values and tools used by developers to
map different development activities carried out during software development from their initial

System Analysis 3
stages to completion (Himadri & Dr. Birendra, 2015). Many development frameworks have
evolved since the advent of systems’ and software development and each is identified with
associated strengths and weaknesses. Based on organizational requirements or the nature of
system/software to be developed, development team choose the best suited development
methodologies. This choice is also influenced by both technical, organizational and development
team considerations.
The situation at the Allsports Sports Club (ASC) requires that agile development
methodology is used. Agile methodologies are based on incremental iterative approaches and are
open to changing user requirements. Using these methodologies, developers get constantly get
user feedback after every iterative cycle. The computer system required by the organization is a
complicated one and requires a methodology approach that anticipates change and that is highly
flexible. The product delivered in the initial stages will constantly be improved until a final
product that meet client’s requirements is delivered (Sharma, et al., 2012). This way, it will be
possible for the development team to schedule meetings with the clients and review work
progress. The overall development cost will be lowered while evaluation time will be speeded
up. This is because evaluation and development are conducted in parallel.
4. Data Gathering Techniques
Exhaustive requirements elicitation is critical for the success of software development
projects. Requirements analysis, which is the initial development phase can cripple the whole
project if poorly done. Data gathering techniques ensures full stakeholder involvement thus
ensuring that user requirements are fully understood before commencing on other development
phases (Lethbridge, et al., 2005). Additionally, appropriate requirements gathering techniques
are required to ensure that correct requirements are gathered and accurately analyzed and

System Analysis 4
documented. The techniques used here helps the development team unmask both the functional
and non-functional system requirements. To better understand requirements for the ASC system,
I would use interviews, questionnaires and focus group sessions techniques.
Interviews are the most popular requirements gathering techniques that involves
stakeholders and system’s analysts. The interviewed parties or user groups are either the
management, expected users, users that interact with the current system (in case of a system
replacement) and system financiers among other groups (Laplante, 2017). Interviews are aesy to
conduct- face to face, through a phone call and can range from in-depth to semi-structured
excercise with both open-ended and closed questions.
Through this technique, it will be easier for me to uncover in-depth information. I will
also be in a position to get people’s opinions and knowledge in regard to the current system and
the proposed one. Response rate’s significance may be improved by the presence of a trained
interviewer since it increases respondents’ conciousness. This way, I will be assured of getting
more accurate data/information with minimal ambiguity.
Focus group sessions involves discussing the proposed system with the relevant people-
mostly end users and the management. This way, a lot of information is ‘mined’ within a short
period of time (Mamoun, 2015). Requirements or ideas that might have been overlooked before
might resurface together with their significance thus giving the analyst a better understanding of
the product that they are expected to deliver. The system required at the ASC is a broad one and
requires such a data gathering technique.
A set of questions structured in a document called questionnaire can be used to collect
information too. Questionnaires become very useful in the process of requirement gathering in

System Analysis 5
situations where there are many users (expected), distributed in different geographical locations
and whose inputs are considered as being critical for the understanding of the proposed system’s
features (Ramdhani, et al., 2018). To ensure that users complete the questionnaires, I will ensure
that they are not too long and structure the questions to take the form of WH and HOW
questions.
It is expected that the proposed ASC system will have large number of users (1000) and
their input is, therefore, important. This exercise will take less time compared to interviews and
will give the respondents enough time to brainstorm and develop sound reasoning/judgement. It
is an opportunity for the system analysts to precisely structure and formulate data collection
plans that will lead to eased analysis. Additionally, it will be easy to reach the respondents using
such means as email and the internet.
5. Sample Questionnaire
Section one: Introduction
In order to streamline its services, Allsports Sports Club (ASC), a multisport club with
over 1000 members and offering diverse sports activities, has decided to develop a new system.
It is expected that this system will be enhanced to cater for the growing membership, and avoid
difficulties in accessing information. It is in this regard that we are undertaking this research with
an aim of understanding your experience with the current system as well as your expectations
from the proposed one. Welcome and kindly feel free to share with us any information that may
help us deliver the best. We promise to keep all information provided as private and confidential.

System Analysis 6
Section two: Demographic Data
Name (optional): _______________________________________
Email adress (optional): __________________________________
Age bracket (please tick as appropriate): 9-15 16-24 24-30 above 30
Gender: Male
Female
Sport Taken (please indicate the sport you participate in in ASC): _________________________
Section three: Questions
a) Rate your ease of using spreadsheet and word processors on a scale of 1 to 5.
1 Very easy and
good to use
2 Slightly easy
and good
3 Neutral
4 Not that easy
5 Very difficult
and extremely
bad to use.
b) Are you farmiliar with spreadsheet and word processor?
Answer _______________
c) List difficulties (if any) that you face when working with the above applications.
Answers: ________________________________________________________
________________________________________________________
d) Calculations on spreadsheet and word processor are easy or not.
Answer: ___________________________________________

System Analysis 7
e) How much accurate are the calculations that you get using these applications? Choose
one option only.
o Accurate results.
o Few mistakes.
o Not correct at all
f) Information retrieval from the current system is easy (select one option)
ο Strongly agree
ο Agree
ο Do not know
ο Disagree
ο Strongly disagree
g) Do the above mentioned applications maintain data consistency?
Answer: ______________________
h) Would you like to switch to a new system?
Answer: ______________
i) What are the features of the system that you would wish to switch to?
Answers: _________________________________________________
j) What problems have yu experienced while working with the current system?
Answers: _____________________________________________
Thank you for having time with us.
6. Functional and Non-Functional Requirements

System Analysis 8
The final outcome of a software development cycle depends on the context on which
functional and non-functional requirements are defined. Though the two ‘collide’, they should
not be seperated and must be integrated in the overall system’s architecture. While functional
requirements define what a new software product should do, non-functional requirements
describe how certain operations should be performed by the system. Functional requirements
define a particular system’s behavior function when certain conditions are met.
Functional requirements
The functional requirements for the ASC include data processing, historical data, data
entry, report generation and accurate calculations.
a) Data entry- the system should be in apposition to store all information/data regarding the
players, and sport club’s activities with a lot of accuracy while maintaining consistency.
b) Data processing- user requests should be performed within the minimum time possible.
c) Historical data and report generation- both the management and the players should be in a
position to retrieve data based on various filters or criteria. All events as listed in the
system should be accessible to authorized users.
d) Accurate calculations- the manual calculations should be replaced by automated and
accurate ones.
Non-functional requirements
These requirements describe the new system’s behavior and its limits on its
functionalities. The following describe the proposed system’s attributes and characteristics.
a) Data integrity- the system should ensure that in all data states- rest, transition or being
processed should not be manipulated b unauthorized parties.

System Analysis 9
b) Reliability- the system services should be available at all times to ensure maximum
throughput and user satisfaction.
c) Performance- simultaneous transactions or processes should be processed without error
or failure while marinating the atomicity property.
d) Robustness- system should recover from error effectively.
e) Usability- enhance user experience and interaction by using standard design principles.
Section B: Data Modelling
1. Class Diagrams
These are structural diagram that depict how objects of different types are related to each
other and the functions that they can perform. A class is identified using a name, has attributes
and methods through which its objects can either be publicly or privately accessed or otherwise
manipulated (Cunha, et al., 2015). The ASC system will have three classes- AffiliateIndividuals,
Bulletin and Advertisers.
The class named affiliate members that will have all members’ information such as a
name, address, phone numbers, email addresses, and a sport that they play. This class can be
manipulated by such methods as addmember (), deletemember (), member_sportplayed (),
member_editednewsletter (), and reademail () among others. The Bulletin class will store
information regarding all publications- title, editor, date published, article’s file name,
advertisement details, advert identifier and subject among others. An article can be added, edited,
deleted, or be meant for publishing purposes. Advertisers’ class will be used to give info about
advertisers who publish articles in the system. Every technique in this design will be utilizing its

System Analysis 10
own data from their correlative class and each function will be associated with its own database.
Below is a class diagram for the proposed system.
Figure 1: Class diagram
2. Use Case Diagrams
These can be described as both structural and behavioral UML diagrams that depict
interactions between different elements of a system (Singh, et al., 2016). The following diagrams
show hoe different elements will be interacting with each other in the ASC system.

System Analysis 11
Figure 2: Use case 1
Figure 3: Use case 2
3. Use Case scenarios

System Analysis 12
Use Case 1
In this scenario, the president choose an editor among the affiliated members for every
bulletin that is to be published. The chosen editor is then tasked with the responsibility of
publicizing articles and adverts on pamphlets. The president can see details for the publicized
articles and advertisements.
Use Case 2
In this scenario, the president of the sports club takes charge of purifying and evaluating
the entire framework. He first chooses an editor from the list of affiliated members, and this
editor can add articles, advertisements, publicize bulletin and even generate a report of all
publications made.

System Analysis 13
4. Entity Relationship Diagram
Figure 4: ERD Diagram

System Analysis 14
5. Data Flow diagram
Figure 5: DFD diagram

System Analysis 15
6. Activity Diagram
Figure 6: Activity Diagram

System Analysis 16
This activity diagram uses top-to-bottom approach, a choice that is influenced by the
scenarios in the use case.
7. Interface design
Well-designed user interfaces are based on aesthetics and heuristic principles that
enhance user performance and interaction with a system. Such interfaces are easy to learn and
use and are designed with user ‘at the centre.’ For the ASC system, the functionalities such as
invoicing, affiliate member management, adding bulletin and articles requires that interfaces
‘minimally’ designed. The following diagrams represent design for these functionalities.

System Analysis 17
Figure 7: implementation of invoicing interface
Figure 8: an implementation of user management interface

System Analysis 18
Figure 9: a bulletin management interface

System Analysis 19
Figure 10: article management interface

System Analysis 20
8. Conclusion
Development of a new system at the ASC is a complicated undertaking. Due to the
expected changes in user requirements, agile development methodologies are best suited to solve
the problem. Agile methodologies are highly flexible and iterative- allowing stakeholder’s
participation after each iteration cycle. It also makes it easy to develop a product that meet
client’s needs since evaluation and development are run parallel to each other. Interviews,
questionnaires and focus group interview are the most accurate techniques to gather user
requirements. This is due to the fact that the club’s membership is large and going by the fact
that requirements must be understood well before commencing other phases. Functional
requirements for the system include accuracy, data entry, report generation, and historical data
management while the non-functional ones include performance, robustness, data integrity and
performance.

System Analysis 21
9. References
Cunha, A., Ana, G. & Daniel, R., 2015. Translating between Alloy specifications and UML class
diagrams annotated with OCL. Software & Systems Modeling, 14(1), pp. 5-25.
Himadri, B. M. & Dr. Birendra, G., 2015. Selection of Software Development Methodology
(SDM): A Comparative Approach. International Journal of Advanced Research in Computer
Science and Software Engineering, 5(3), pp. 58- 60.
Laplante, P. A., 2017. Requirements engineering for software and systems. s.l.:Auerbach
Publications.
Lethbridge, T. C., Susan, E. S. & Janice, S., 2005. Studying software engineers: Data collection
techniques for software field studies. Empirical software engineering, 10(3), pp. 311-341.
Mamoun, E., 2015. Requirement Gathering Methods. [Online]
Available at: https://www.umsl.edu/~sauterv/analysis/F2015/Requirement%20Gathering
%20Methods.html.htm
[Accessed 13 september 2019].
Ramdhani, M. A., Dian, S. M., Abdusy, S. A. & Hilmi, A., 2018. Requirements elicitation in
software engineering. International Journal of Engineering & Technology (UEA), 7(19), pp.
772-775.
Sharma, S., Darothi, S. & Divya, G., 2012. Agile processes and methodologies: A conceptual
study. International journal on computer science and Engineering, 4(5), p. 892.
Singh, M., Sharma, A. K. & Ruhi, S., 2016. Formal Transformation of UML Diagram: Use
Case, Class, Sequence Diagram with Z Notation for Representing the Static and Dynamic

System Analysis 22
Perspectives of System. Singapore, Springer.