Systems Analysis and Design of Allsports Sports Club: Case Study

This assignment analyzes the Systems Analysis and Design for the Allsports Sports Club. The solution covers various aspects of the club's information system, including class diagrams, use case diagrams, entity-relationship diagrams, and activity diagrams. The document examines how the club's newsletter, The Sports Report, is managed, from member contributions to publication. The analysis includes the interaction between the president, members, and the system, focusing on data flow, user roles, and system interfaces. The assignment also addresses the assumptions made in the design process, such as the need for a simple interface and the importance of error checking. Overall, the assignment aims to provide a comprehensive understanding of the system's architecture and functionality, highlighting the key components and processes involved in managing the club's operations.

Systems Analysis and Design: Allsports Sports Club
Name
Institution
Professor
Course
Date

1. Class diagrams
Class diagram is composed of four different classes which outlines the interacting
entities in The Sports Report Information System (TSRIS). The main class is member
which entirely supports all other classes. Without member class, all other classes cannot
operate. Assumptions are; president would be able to select required content of the report
that suits specific needs. The next assumption is that president would generate report by
click of a button with need to write SQL queries.

2. Use case diagrams
A use case diagram in this case represents interaction between actors and The
Sports Report Information System (TSRIS). All actors should be registered in order to
interact with system. The assumptions are; president would register the register all
sporting members who are to take part in publication. Similarly, member would be able
to perform different activities depending on privileges granted.

3. Use case scenarios
Use Case ID Primary Actor Use Cases
President Yes Login, register member, Register sport, get report
Member Yes Login, publish and edit newsletter

4. Entity Relationship Diagram
The flow of data presented in this case would be specific depending on the user
using the system. After login, the user would select the relevant module and execute
required duties. In this case, member would be able to login, publish newsletter and edit
depending on privileges granted by the president. Assumptions are; database would be in
atomic state to facilitate smooth information search.

5. Context Diagram
The interaction between two actors and the system are guided by role they play.
Member writes content for publication and submits it to the system for consideration. In
return, writer is compensated on all publications made for sporting activities. President
can view all publications and members contributions as well make decision based
publications available. Assumptions are; president would make decision based on
publications made and feedback from several reviews from readers.

6. Activity Diagram
The flow of information is sequential in nature from session created during login
to exit of the system. The assumptions are; all articles must be presented for
consideration. The next assumption is that, unless user has been registered and granted
privileges, publication cannot be done. The final assumption is on error checking, once an
article has errors, it should not be allowed to proceed to the next stage of publication.

7. ASC Interfaces
The design of any information system interface should be guided by design
principles. These principles are; simple interface, ease of accessing menus and location of
buttons. Assumptions are; there should be approvals before some publications can be
done. The other assumption is that, ASC system would be online for ease of access from
anywhere.