System Analysis and Design
VerifiedAdded on  2023/03/17
|17
|2006
|32
AI Summary
This report discusses the development of an information system for Allsports club to track newsletter and advertiser details. It covers the chosen software development methodology, data gathering techniques, functional and non-functional requirements, and more.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Section A.........................................................................................................................................2
Introduction..................................................................................................................................2
Chosen Software Development Methodology.............................................................................2
Data Gathering Techniques.........................................................................................................3
Questionnaire...............................................................................................................................3
Functional and Non-Functional Requirements............................................................................4
Conclusion...................................................................................................................................5
Section B..........................................................................................................................................6
1. Class diagram...........................................................................................................................6
2. Use Case Diagram...................................................................................................................7
3. Use Case scenarios..................................................................................................................8
4. Entity Relationship Diagram.................................................................................................10
5. Data Flow Diagram................................................................................................................11
6. Activity Diagram...................................................................................................................12
7. Interface.................................................................................................................................13
References......................................................................................................................................15
Table of Contents
Section A.........................................................................................................................................2
Introduction..................................................................................................................................2
Chosen Software Development Methodology.............................................................................2
Data Gathering Techniques.........................................................................................................3
Questionnaire...............................................................................................................................3
Functional and Non-Functional Requirements............................................................................4
Conclusion...................................................................................................................................5
Section B..........................................................................................................................................6
1. Class diagram...........................................................................................................................6
2. Use Case Diagram...................................................................................................................7
3. Use Case scenarios..................................................................................................................8
4. Entity Relationship Diagram.................................................................................................10
5. Data Flow Diagram................................................................................................................11
6. Activity Diagram...................................................................................................................12
7. Interface.................................................................................................................................13
References......................................................................................................................................15
2SYSTEM ANALYSIS AND DESIGN
Section A
Introduction
The case study of Allsports Club state it as a multisport club having thousand members
takes part in the sporting activities arranged in the club.
The main purpose of this report is developing an information system for Allsports club so
that they can keep a track on all the details related with newsletter and the advertiser details in
the system.
The problem that is identified for the system is that it was difficult to keep track on all the
details of the newsletter every week and that was resulting in delay publication of the newsletter.
As a result, a dissatisfaction was caused in the members of the club. To overcome this, the new
information system is to be analysed and developed. The information system is to be approved
by the President of the club.
Chosen Software Development Methodology
The approaches of SDLC is considered as a framework that helps to make the structure of
the information system, plan the information system and also control the development process of
the information system of the project (Stark, 2015). Approaches that are used are Agile
development, dynamic modelling, XP programming, LD development, prototyping approach and
scrum techniques. Two of the approaches that can be used for developing the information system
of Allsports club is explained below.
Agile methodology is one of the best SDLC approaches that can be used for developing
the information system (Kerzner & Kerzner, 2017). This approach is a framework that is mainly
Section A
Introduction
The case study of Allsports Club state it as a multisport club having thousand members
takes part in the sporting activities arranged in the club.
The main purpose of this report is developing an information system for Allsports club so
that they can keep a track on all the details related with newsletter and the advertiser details in
the system.
The problem that is identified for the system is that it was difficult to keep track on all the
details of the newsletter every week and that was resulting in delay publication of the newsletter.
As a result, a dissatisfaction was caused in the members of the club. To overcome this, the new
information system is to be analysed and developed. The information system is to be approved
by the President of the club.
Chosen Software Development Methodology
The approaches of SDLC is considered as a framework that helps to make the structure of
the information system, plan the information system and also control the development process of
the information system of the project (Stark, 2015). Approaches that are used are Agile
development, dynamic modelling, XP programming, LD development, prototyping approach and
scrum techniques. Two of the approaches that can be used for developing the information system
of Allsports club is explained below.
Agile methodology is one of the best SDLC approaches that can be used for developing
the information system (Kerzner & Kerzner, 2017). This approach is a framework that is mainly
3SYSTEM ANALYSIS AND DESIGN
considered for conducting engineering projects. Another method that can be used for developing
this system is prototyping approach. The reasons to select these methods are discussed below.
Agile methodology helps the developer to focus on the software of the information
system and mainly focuses on the work that is in progress. Agile method includes real time
communication within the project (Tao et al., 2017). The prototyping methodology helps the
customer to evaluate the requirements and the developers take the help of the users to develop
the system. This approach gives more flexible design as well as development of the system and
ends in more accurate system.
Data Gathering Techniques
The data gathering techniques that are used for developing the information system are
explained below:
Questionnaire: This a method of data collection that will administer the sample subjects
and the questionnaire can be carried out through phone, email, online or face to face
(Ogharaduku et al., 2016). The plan of the information system and the structure can be
formulated easily with the questionnaire data collection technique.
Interviews: This method is carried out to overcome the drawbacks of an information
system (Hughes, 2016). Data can be collected through interviews related to the existing system
and the new information system the users wants to be developed.
Group Session: This particular method is carried out while the developing process is in
process (Nuno & John, 2015). This methods helps the developer to take the discussion in next
level and develop the information system more efficiently.
considered for conducting engineering projects. Another method that can be used for developing
this system is prototyping approach. The reasons to select these methods are discussed below.
Agile methodology helps the developer to focus on the software of the information
system and mainly focuses on the work that is in progress. Agile method includes real time
communication within the project (Tao et al., 2017). The prototyping methodology helps the
customer to evaluate the requirements and the developers take the help of the users to develop
the system. This approach gives more flexible design as well as development of the system and
ends in more accurate system.
Data Gathering Techniques
The data gathering techniques that are used for developing the information system are
explained below:
Questionnaire: This a method of data collection that will administer the sample subjects
and the questionnaire can be carried out through phone, email, online or face to face
(Ogharaduku et al., 2016). The plan of the information system and the structure can be
formulated easily with the questionnaire data collection technique.
Interviews: This method is carried out to overcome the drawbacks of an information
system (Hughes, 2016). Data can be collected through interviews related to the existing system
and the new information system the users wants to be developed.
Group Session: This particular method is carried out while the developing process is in
process (Nuno & John, 2015). This methods helps the developer to take the discussion in next
level and develop the information system more efficiently.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4SYSTEM ANALYSIS AND DESIGN
Questionnaire
The questionnaire below can be asked to the users of the information system.
1. Are you facing any difficulty with the current working process of the Allsports Club? If
yes, point out the problems.
2. What are your roles in this system?
3. What features are you expecting from the new information system?
4. What platform are you using for the current system?
5. Do you have any special feature added to the information system?
6. There is a need of handling the report process. How to you expect to manage it?
7. Do you like to have a usability test after the software being developed?
8. Does the software need to have a supporting features for the visually impaired people?
9. What are the technologies to be used for information system?
10. Who are associated with this project handling this application system?
Functional and Non-Functional Requirements
Functional requirements that are included in the system are:
1. The system will take the input of all the club members associated with Allsports.
2. The system will take input of all the articles that are to be uploaded by the members.
3. The system will store the details of the advertisers in the system (Khan et al., 2016).
4. The system will help in storing all the details of all the newsletter that are published every
week.
5. All the news article writers for every week are also kept in the system.
Questionnaire
The questionnaire below can be asked to the users of the information system.
1. Are you facing any difficulty with the current working process of the Allsports Club? If
yes, point out the problems.
2. What are your roles in this system?
3. What features are you expecting from the new information system?
4. What platform are you using for the current system?
5. Do you have any special feature added to the information system?
6. There is a need of handling the report process. How to you expect to manage it?
7. Do you like to have a usability test after the software being developed?
8. Does the software need to have a supporting features for the visually impaired people?
9. What are the technologies to be used for information system?
10. Who are associated with this project handling this application system?
Functional and Non-Functional Requirements
Functional requirements that are included in the system are:
1. The system will take the input of all the club members associated with Allsports.
2. The system will take input of all the articles that are to be uploaded by the members.
3. The system will store the details of the advertisers in the system (Khan et al., 2016).
4. The system will help in storing all the details of all the newsletter that are published every
week.
5. All the news article writers for every week are also kept in the system.
5SYSTEM ANALYSIS AND DESIGN
The non-functional requirements associated with the system are:
1. The system will support usability as the system will have a good interface that will helps
the users to handle the system.
2. The system will be reliable as the data stored in the system will be secured and the
system will support exception handling.
3. The performance of new system will be robust as the system will be able to support
numerous users at a same time (Laplante, 2017).
4. The system will also support extension of the system in future and the system will be
maintained by the president associated with Allsports club.
Conclusion
A Newsletter is published every week by ASC club with president’s supervision. An
editor is selected for editing the newsletter and the editor is appointed by club’s president. The
editor of the club selects ten articles for newsletter from the articles given by the members of the
club. The articles published in the newsletter features the main highlights of the previous week in
their respective sports. There are five advertisements that are also selected from the differ
advertiser by the editor.
This report details the new information system (TSRIS) for the Allsports club. For
developing the information system, two software development were discussed in the report with
three data gathering techniques that helps in collecting data related to the case study. There is a
questionnaire stated above in this report to gather the requirement for developing the information
system. The functional as well as the non-functional requirements are also explained in the report
above that is related to the case study of ASC.
The non-functional requirements associated with the system are:
1. The system will support usability as the system will have a good interface that will helps
the users to handle the system.
2. The system will be reliable as the data stored in the system will be secured and the
system will support exception handling.
3. The performance of new system will be robust as the system will be able to support
numerous users at a same time (Laplante, 2017).
4. The system will also support extension of the system in future and the system will be
maintained by the president associated with Allsports club.
Conclusion
A Newsletter is published every week by ASC club with president’s supervision. An
editor is selected for editing the newsletter and the editor is appointed by club’s president. The
editor of the club selects ten articles for newsletter from the articles given by the members of the
club. The articles published in the newsletter features the main highlights of the previous week in
their respective sports. There are five advertisements that are also selected from the differ
advertiser by the editor.
This report details the new information system (TSRIS) for the Allsports club. For
developing the information system, two software development were discussed in the report with
three data gathering techniques that helps in collecting data related to the case study. There is a
questionnaire stated above in this report to gather the requirement for developing the information
system. The functional as well as the non-functional requirements are also explained in the report
above that is related to the case study of ASC.
6SYSTEM ANALYSIS AND DESIGN
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
7SYSTEM ANALYSIS AND DESIGN
Section B
1. Class diagram
Figure 1: Class Diagram of TSRIS
(Source: Created by Author on Visio)
Section B
1. Class diagram
Figure 1: Class Diagram of TSRIS
(Source: Created by Author on Visio)
8SYSTEM ANALYSIS AND DESIGN
2. Use Case Diagram
For Member Sign Up
Figure 2: Use Case for Member Sign Up
(Source: Created by Author on Visio)
2. Use Case Diagram
For Member Sign Up
Figure 2: Use Case for Member Sign Up
(Source: Created by Author on Visio)
9SYSTEM ANALYSIS AND DESIGN
Use Case for Advertiser
Figure 3: Use Case for Advertiser
(Source: Created by Author on Visio)
3. Use Case scenarios
Overview
Title Use Case Diagram for Club Member Sign Up
Description The members of the club needs to sign up for enrolling themselves as
member of the club and this use case take the details of the club
members to store the data in the system. The club also have to upload
their articles related to their respective sports and they needs to enter
their sports in the system.
Actors Involved Actors involved are club members and administrator
Pre- Conditions A proper interface is needed for the users so that they can enter their
Use Case for Advertiser
Figure 3: Use Case for Advertiser
(Source: Created by Author on Visio)
3. Use Case scenarios
Overview
Title Use Case Diagram for Club Member Sign Up
Description The members of the club needs to sign up for enrolling themselves as
member of the club and this use case take the details of the club
members to store the data in the system. The club also have to upload
their articles related to their respective sports and they needs to enter
their sports in the system.
Actors Involved Actors involved are club members and administrator
Pre- Conditions A proper interface is needed for the users so that they can enter their
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
10SYSTEM ANALYSIS AND DESIGN
details in the system.
Post- Conditions After signup, the club members will be able to upload their articles for
the newsletter.
Exceptions:
1. The process of sign up is not complete and the user needs to provide the details once again.
2. The system takes much time to respond.
Overview
Title Use Case Diagram for Advertisers
Description The advertisers has to sign up in the system in case of the first time
user. Otherwise the advertiser has to login in the system. After
completing the login process, the advertiser has to upload the
advertisement that they want to be in the newsletter and makes the
payment accordingly.
Actors Involved Advertiser and administrator.
Pre- Conditions Notification is to be given about advertisement in the newsletter.
Post- Conditions The editor needs to select the advertisements that are to be added to the
newsletter.
Exceptions:
1. The advertisers needs to sign up in order to login.
details in the system.
Post- Conditions After signup, the club members will be able to upload their articles for
the newsletter.
Exceptions:
1. The process of sign up is not complete and the user needs to provide the details once again.
2. The system takes much time to respond.
Overview
Title Use Case Diagram for Advertisers
Description The advertisers has to sign up in the system in case of the first time
user. Otherwise the advertiser has to login in the system. After
completing the login process, the advertiser has to upload the
advertisement that they want to be in the newsletter and makes the
payment accordingly.
Actors Involved Advertiser and administrator.
Pre- Conditions Notification is to be given about advertisement in the newsletter.
Post- Conditions The editor needs to select the advertisements that are to be added to the
newsletter.
Exceptions:
1. The advertisers needs to sign up in order to login.
11SYSTEM ANALYSIS AND DESIGN
4. Entity Relationship Diagram
Figure 4: Entity Relationship Diagram of TSRIS
(Source: Created by Author on Visio)
4. Entity Relationship Diagram
Figure 4: Entity Relationship Diagram of TSRIS
(Source: Created by Author on Visio)
12SYSTEM ANALYSIS AND DESIGN
5. Data Flow Diagram
Figure 5: Data Flow Diagram of TSRIS
(Source: Created by Author on Visio)
5. Data Flow Diagram
Figure 5: Data Flow Diagram of TSRIS
(Source: Created by Author on Visio)
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
13SYSTEM ANALYSIS AND DESIGN
6. Activity Diagram
Figure 6: Activity Diagram of TSRIS
(Source: Created by Author on Visio)
6. Activity Diagram
Figure 6: Activity Diagram of TSRIS
(Source: Created by Author on Visio)
14SYSTEM ANALYSIS AND DESIGN
7. Interface
Sign Up Interface
Login Interface
7. Interface
Sign Up Interface
Login Interface
15SYSTEM ANALYSIS AND DESIGN
Select Editor Interface
Advertiser Interface
Select Editor Interface
Advertiser Interface
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
16SYSTEM ANALYSIS AND DESIGN
References
Hughes, M. (2016). Interviewing. Research methods for postgraduates, 264-274.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), 7-
13.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Nuno, A., & John, F. A. S. (2015). How to ask sensitive questions in conservation: A review of
specialized questioning techniques. Biological Conservation, 189, 5-15.
Ogharaduku, B. E., Jubb, D., Lochrie, S., Curran, R. W. F. A., & O'Gorman, K. D. (2016).
Methods and Techniques for Qualitative Data Gathering. In Research Methods for
Accounting and Finance (pp. 123-141). Goodfellow Publishers.
Stark, J. (2015). Product lifecycle management. In Product lifecycle management (Volume
1) (pp. 1-29). Springer, Cham.
Tao, J., Chen, Z., Yu, S., & Liu, Z. (2017). Integration of Life Cycle Assessment with computer-
aided product development by a feature-based approach. Journal of cleaner
production, 143, 1144-1164.
References
Hughes, M. (2016). Interviewing. Research methods for postgraduates, 264-274.
Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), 7-
13.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Nuno, A., & John, F. A. S. (2015). How to ask sensitive questions in conservation: A review of
specialized questioning techniques. Biological Conservation, 189, 5-15.
Ogharaduku, B. E., Jubb, D., Lochrie, S., Curran, R. W. F. A., & O'Gorman, K. D. (2016).
Methods and Techniques for Qualitative Data Gathering. In Research Methods for
Accounting and Finance (pp. 123-141). Goodfellow Publishers.
Stark, J. (2015). Product lifecycle management. In Product lifecycle management (Volume
1) (pp. 1-29). Springer, Cham.
Tao, J., Chen, Z., Yu, S., & Liu, Z. (2017). Integration of Life Cycle Assessment with computer-
aided product development by a feature-based approach. Journal of cleaner
production, 143, 1144-1164.
1 out of 17
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024  |  Zucol Services PVT LTD  |  All rights reserved.