QAC020C154S - System Design for Icon College Information System
VerifiedAdded on 2023/04/21
|7
|1552
|416
Report
AI Summary
This report outlines the system design for Icon College's new information system, focusing on incorporating all college activities into a unified system. It details the project's scope, including use case, interaction, and sequence diagrams, and addresses the project's complexity, emphasizing the importance of considering both client and user perspectives. The agile methodology is chosen for software development, highlighting its iterative approach and real-time communication benefits. The report also identifies areas for improvement in the design process, such as workflow creation, backlog management, work-in-progress control, progress visualization, and clear definition of completion criteria. Key recommendations include improved communication, continuous testing, and iterative development for future system software designs.

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
Coursework 2: System Design.........................................................................................................2
Scope of the Project.........................................................................................................................2
Complexity of the Project................................................................................................................2
Choosing Software Development Methodology.............................................................................3
Designing the Improvement Areas and Recommendations.............................................................4
References........................................................................................................................................6
Table of Contents
Coursework 2: System Design.........................................................................................................2
Scope of the Project.........................................................................................................................2
Complexity of the Project................................................................................................................2
Choosing Software Development Methodology.............................................................................3
Designing the Improvement Areas and Recommendations.............................................................4
References........................................................................................................................................6

2SYSTEM ANALYSIS AND DESIGN
Coursework 2: System Design
Scope of the Project
The scope of the project is to design a system that for the new information of the icon
College. The Icon College wants to include all its activities in an information system. The main
aim of this report is to design the system of the information system of the college.
The specific goal that this report includes is designing the system for the information
system for the college. For designing the new information system, use case diagram, interaction
diagram and the sequence diagram is addressed in this report that is related to the information
system.
The objectives that are included in this paper are-
To study the new information system of the Icon College System.
To design the system that includes the use case diagram, interaction diagram, the class
diagram, and the sequence diagram related to the system.
To study the complexity of the undertaken project and providing some recommendations
for improving the design of the system.
Complexity of the Project
Designing of system includes determination of the interdependent variables. While
designing a system, the point of view of the client and the users are both to be kept in mind by
the developer of the system (Ojala et al., 2017). There are many approaches of model that can be
adopted by the developer for calculating different aspects of designing the system and different
views are also considered for the system that is to be designed. The traditional user interface that
Coursework 2: System Design
Scope of the Project
The scope of the project is to design a system that for the new information of the icon
College. The Icon College wants to include all its activities in an information system. The main
aim of this report is to design the system of the information system of the college.
The specific goal that this report includes is designing the system for the information
system for the college. For designing the new information system, use case diagram, interaction
diagram and the sequence diagram is addressed in this report that is related to the information
system.
The objectives that are included in this paper are-
To study the new information system of the Icon College System.
To design the system that includes the use case diagram, interaction diagram, the class
diagram, and the sequence diagram related to the system.
To study the complexity of the undertaken project and providing some recommendations
for improving the design of the system.
Complexity of the Project
Designing of system includes determination of the interdependent variables. While
designing a system, the point of view of the client and the users are both to be kept in mind by
the developer of the system (Ojala et al., 2017). There are many approaches of model that can be
adopted by the developer for calculating different aspects of designing the system and different
views are also considered for the system that is to be designed. The traditional user interface that

3SYSTEM ANALYSIS AND DESIGN
were used previously mainly had concern with only one user and includes a monolithic system
(Moreno et al., 2016). But for the Icon College system designing, the developer has established
the concern of both the user and the clients while designing the system and had a clear
conversation between the users and the client. The developer has also included the distributed
computing as well as system networking that is relevant to the user. The main aim of the user
interface is mainly to design a system for the college (Mens, 2016). Collecting all the
information at one time was very much complex part of the project and modelling the
requirement and analyzing it was another complex part of designing the system for the Icon
College.
Choosing Software Development Methodology
The software development methodology that is chosen by the developer for developing
the new information system is agile methodology of software development (Harned, 2018). As
the designing of the software done as per the requirement of the user and the client, the system
developed is to be tested in different phases of developing. The Agile methodology is basically a
framework that is undertaken for the projects involved in software engineering (Abrahamsson et
al., 2017). Using the agile methodology of designing the software usually minimizes the risks
that are involved in developing the software. The agile methodology divides the system in the
small time boxes that are known as iterations in the development phase (Vijayasarathy & Butler,
2016). In agile methodology, the iterations are considered as iteration projects and includes all
the steps that are required in releasing the new functionality including planning, analyzing the
requirements, designing, coding, software testing, and finally documenting the software.
were used previously mainly had concern with only one user and includes a monolithic system
(Moreno et al., 2016). But for the Icon College system designing, the developer has established
the concern of both the user and the clients while designing the system and had a clear
conversation between the users and the client. The developer has also included the distributed
computing as well as system networking that is relevant to the user. The main aim of the user
interface is mainly to design a system for the college (Mens, 2016). Collecting all the
information at one time was very much complex part of the project and modelling the
requirement and analyzing it was another complex part of designing the system for the Icon
College.
Choosing Software Development Methodology
The software development methodology that is chosen by the developer for developing
the new information system is agile methodology of software development (Harned, 2018). As
the designing of the software done as per the requirement of the user and the client, the system
developed is to be tested in different phases of developing. The Agile methodology is basically a
framework that is undertaken for the projects involved in software engineering (Abrahamsson et
al., 2017). Using the agile methodology of designing the software usually minimizes the risks
that are involved in developing the software. The agile methodology divides the system in the
small time boxes that are known as iterations in the development phase (Vijayasarathy & Butler,
2016). In agile methodology, the iterations are considered as iteration projects and includes all
the steps that are required in releasing the new functionality including planning, analyzing the
requirements, designing, coding, software testing, and finally documenting the software.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.

4SYSTEM ANALYSIS AND DESIGN
Agile methodology includes real-time communication which is very much useful for
designing the system software for the college. There must be a clear communication between the
users and the client with the system developer (Matharu et al., 2015). The communication that is
established in agile methodology software development preferably includes face to face
communication or in written documents. The developer first defines the system that includes
product managers, analysts of the business and the customers associated (Giardino et al., 2016).
The methodology of agile project management mainly emphasize the software as the main
measure of the progress that is included in the system.
Designing the Improvement Areas and Recommendations
For designing the system software, the improvement areas that the developer will address
while designing a software in future are stated below:
Creating a workflow: Workflow is a process that is needed to be maintained by every
developer involved in system designing. The state of the workflow is much more
complicated than can be seen in real life. The tasks involve din system designing usually
goes through many stages that includes planning, testing, reviewing, as well as deploying.
All the tools included in software designing is to be customize by the developer.
Cleaning the backlogs: It is actually expected from a developer that they will provide
new ideas for developing a system software. The developer designing the new
information system of the Icon College has taken idea from other information system of
different colleges. Product backlog helps to focus on the important work rather than other
different work.
Agile methodology includes real-time communication which is very much useful for
designing the system software for the college. There must be a clear communication between the
users and the client with the system developer (Matharu et al., 2015). The communication that is
established in agile methodology software development preferably includes face to face
communication or in written documents. The developer first defines the system that includes
product managers, analysts of the business and the customers associated (Giardino et al., 2016).
The methodology of agile project management mainly emphasize the software as the main
measure of the progress that is included in the system.
Designing the Improvement Areas and Recommendations
For designing the system software, the improvement areas that the developer will address
while designing a software in future are stated below:
Creating a workflow: Workflow is a process that is needed to be maintained by every
developer involved in system designing. The state of the workflow is much more
complicated than can be seen in real life. The tasks involve din system designing usually
goes through many stages that includes planning, testing, reviewing, as well as deploying.
All the tools included in software designing is to be customize by the developer.
Cleaning the backlogs: It is actually expected from a developer that they will provide
new ideas for developing a system software. The developer designing the new
information system of the Icon College has taken idea from other information system of
different colleges. Product backlog helps to focus on the important work rather than other
different work.

5SYSTEM ANALYSIS AND DESIGN
Controlling the Work In Progress (WIP): As because of short time period, the
developer has introduced multitasking while developing the system software.
Multitasking most of the time decreases the efficiency of the work. The more amount of
multitasking results in increasing the time to complete a particular task. Setting the work
in progress does not actually means never starting new task prior completing the previous
task. There should be proper guidelines as well as warming signs instead of having
absolute rules.
Making the progress visible: To visualize the work that is in progress is one of the
important thing to do. Managing the activities visually is one of the oldest methods. All
the methods includes in software designing is to be visualized personally by the system
developer. The author can even visualize the work progress by making a flowchart for
detecting the bottlenecks.
Having a clear idea of have “Done”: For a work that is in progress, acceptance criteria
is one of the most important area that helps in ensuring the once the tasks gets completed
not only as per its functionality, but also has a good quality. There are many rules that are
to be followed by a developer. The rules include featuring the software that is being
implemented, passing the unit testing included, the documentation involved in the
software is to be up to date and the feature of the system is to be reviewed by question
answer segment. The code is also to be developed in the production.
Controlling the Work In Progress (WIP): As because of short time period, the
developer has introduced multitasking while developing the system software.
Multitasking most of the time decreases the efficiency of the work. The more amount of
multitasking results in increasing the time to complete a particular task. Setting the work
in progress does not actually means never starting new task prior completing the previous
task. There should be proper guidelines as well as warming signs instead of having
absolute rules.
Making the progress visible: To visualize the work that is in progress is one of the
important thing to do. Managing the activities visually is one of the oldest methods. All
the methods includes in software designing is to be visualized personally by the system
developer. The author can even visualize the work progress by making a flowchart for
detecting the bottlenecks.
Having a clear idea of have “Done”: For a work that is in progress, acceptance criteria
is one of the most important area that helps in ensuring the once the tasks gets completed
not only as per its functionality, but also has a good quality. There are many rules that are
to be followed by a developer. The rules include featuring the software that is being
implemented, passing the unit testing included, the documentation involved in the
software is to be up to date and the feature of the system is to be reviewed by question
answer segment. The code is also to be developed in the production.

6SYSTEM ANALYSIS AND DESIGN
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Giardino, C., Paternoster, N., Unterkalmsteiner, M., Gorschek, T., & Abrahamsson, P. (2016).
Software development in startup companies: the greenfield startup model. IEEE
Transactions on Software Engineering, 42(6), 585-604.
Harned, D. (2018). Hands-On Agile Software Development with JIRA: Design and manage
software projects using the Agile methodology. Packt Publishing Ltd.
Matharu, G. S., Mishra, A., Singh, H., & Upadhyay, P. (2015). Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), 1-6.
Mens, T. (2016). Research trends in structural software complexity. arXiv preprint
arXiv:1608.01533.
Moreno-León, J., Robles, G., & Román-González, M. (2016, April). Comparing computational
thinking development assessment scores with software complexity metrics. In 2016 IEEE
global engineering education conference (EDUCON)(pp. 1040-1045). IEEE.
Ojala, A., Paavilainen-Mäntymäki, E., Su, N., & Lyytinen, K. (2017, August). Software
Complexity and Organization of Firms’ Offshoring Activities. In Scandinavian
Conference on Information Systems (pp. 15-27). Springer, Cham.
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development methodologies:
Do organizational, project, and team characteristics matter?. IEEE software, 33(5), 86-94.
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Giardino, C., Paternoster, N., Unterkalmsteiner, M., Gorschek, T., & Abrahamsson, P. (2016).
Software development in startup companies: the greenfield startup model. IEEE
Transactions on Software Engineering, 42(6), 585-604.
Harned, D. (2018). Hands-On Agile Software Development with JIRA: Design and manage
software projects using the Agile methodology. Packt Publishing Ltd.
Matharu, G. S., Mishra, A., Singh, H., & Upadhyay, P. (2015). Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), 1-6.
Mens, T. (2016). Research trends in structural software complexity. arXiv preprint
arXiv:1608.01533.
Moreno-León, J., Robles, G., & Román-González, M. (2016, April). Comparing computational
thinking development assessment scores with software complexity metrics. In 2016 IEEE
global engineering education conference (EDUCON)(pp. 1040-1045). IEEE.
Ojala, A., Paavilainen-Mäntymäki, E., Su, N., & Lyytinen, K. (2017, August). Software
Complexity and Organization of Firms’ Offshoring Activities. In Scandinavian
Conference on Information Systems (pp. 15-27). Springer, Cham.
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development methodologies:
Do organizational, project, and team characteristics matter?. IEEE software, 33(5), 86-94.
1 out of 7
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.