University System Analysis and Design Project: Allsports Sports Club

This document presents a comprehensive system analysis and design project for the Allsports Sports Club. It includes a variety of diagrams such as class diagrams, use case diagrams, an entity-relationship diagram (ERD), a data flow diagram (DFD), and an activity diagram, all created using Visio. The use case diagrams detail scenarios for member sign-up and editor functions, providing descriptions, actors, pre-conditions, post-conditions, and exceptions. The project also incorporates a questionnaire and waterfall methodology analysis, addressing the club's requirements and system development approach. Finally, the project includes an interface and a bibliography of relevant academic sources.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Section B
1. Class Diagram
Figure 1: Class Diagram for Allsports Sports Club
(Created by Author in Visio)

2SYSTEM ANALYSIS AND DESIGN
2. Use Case Diagram
Use Case Diagram for Member to Sign Up
Figure 2: Use Case Diagram for Member to Sign Up in Allsports Sports Club
(Created by Author in Visio)

3SYSTEM ANALYSIS AND DESIGN
Use case Diagram for Editor
Figure 3: Use Case Diagram for Editor in Allsports Sports Club
(Created by Author in Visio)
3. Use Case Scenarios
Overview
Title Use Case Diagram for membership sign up in Allsports Sports Club
Description For the use case stated in diagram 2, the activities that are involved for
the use case are stated in the diagram. For becoming a member of the
ASC club, a customer should login into the system. Before login they
needs to sign up. The members of the club can uploads advertisements

4SYSTEM ANALYSIS AND DESIGN
so that the editorial board can check them. They can also update their
sports playing ability on their portals so that the editor and the
president gets to know about what kinds of sports the particular
member plays.
The member of the ASC can also logout from the system.
Actors Involved Only one actor is involved in the system. The actor is the member who
login in the system.
Pre- Conditions The system should have a good interface so that the member of the
club does not feel any problem to login or any problem to submit their
articles for the newsletter.
Post- Conditions The login should be done properly with proper passwords and
usernames.
The sign up process should also be done properly.
Exceptions: The editor needs to keep a track on all the members of the club. All members
associated with the club needs to submit the article.
Overview
Title Use Case Diagram for Editor
Description The editor is primarily selected by the president. The editor needs to
login in to the system before proceeding with any activities. The editor
checks all the article form the members of the club. The editor also has
to review the article and then selects those particular articles that are to
be published in the weekly newsletter. The editor also keeps a track on

5SYSTEM ANALYSIS AND DESIGN
the how many articles are submitted by each member of the club. The
editor also needs to logout the system when not using the system.
Actors Involved The use case includes the editor who is responsible for doing all these
activities.
Pre- Conditions The articles are to be uploaded by the members of the club before the
editor to be checked.
Post- Conditions The articles that are selected should be published in the weekly
magazine for that week.
Exceptions: The editor and the members should have a proper communication and maintain a
good relation between them.

6SYSTEM ANALYSIS AND DESIGN
4. Entity Relationship Diagram
Figure 4: ERD for Allsports Sports Club
(Source: Created by Author on Visio)

7SYSTEM ANALYSIS AND DESIGN
5. Data Flow Diagram
Figure 5: DFD of Allsports Sports Club
(Source: Created by Author on Visio)

8SYSTEM ANALYSIS AND DESIGN
6. Activity Diagram
Figure 6: Activity Diagram
(Source: Created by Author on Visio)

9SYSTEM ANALYSIS AND DESIGN
7. Interface

10SYSTEM ANALYSIS AND DESIGN

11SYSTEM ANALYSIS AND DESIGN
8. Bibliography
Dennis, A., Wixom, B.H. and Roth, R.M., 2014. Systems analysis and design. John wiley &
sons.
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Fernández-Sáez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are
Forward Designed or Reverse-Engineered UML diagrams more helpful for code maintenance?:
A family of experiments. Information and Software Technology, 57, pp.644-663.
Jena, A.K., Swain, S.K. and Mohapatra, D.P., 2014, February. A novel approach for test case
generation from UML activity diagram. In Issues and challenges in intelligent computing
techniques (ICICT), 2014 international conference on (pp. 621-629). IEEE.
MacLean, C. and COWIE, G., RAPTOR OIL Ltd, 2018. Data flow graph. U.S. Patent
Application 10/007,496.
Stikkolorum, D.R., Ho-Quang, T. and Chaudron, M.R., 2015, August. Revealing Students' UML
Class Diagram Modelling Strategies with WebUML and LogViz. In Software Engineering and
Advanced Applications (SEAA), 2015 41st Euromicro Conference on (pp. 275-279). IEEE.
Yue, T., Briand, L.C. and Labiche, Y., 2015. aToucan: an automated framework to derive UML
analysis models from use case models. ACM Transactions on Software Engineering and
Methodology (TOSEM), 24(3), p.13.