Object-Oriented Design Review: Cheltenham Football Club System Report

This report provides a review and evaluation of the Cheltenham Football Club Information System, building upon prior coursework. It identifies the project's scope, goals, and tasks, presenting the outcomes and design principles employed. The report compares design choices with industry practices, justifying decisions and explaining the project's complexity. It discusses the role of a system analyst, the application of the object-oriented approach using UML diagrams, and the benefits and drawbacks of the OO paradigm. Key lessons learned are highlighted, along with suggestions for improvements, including the adoption of Agile methodology for future development. The report emphasizes the importance of iterative processes, customer satisfaction, and risk reduction in software development, referencing various academic sources to support its analysis and recommendations.

Coursework 2: Review and Evaluation Report
Coursework 2 is an individual report and will be submitted as a word document (1000
words) and must include the review and evaluation of your work performed in Coursework
1. You should also review and evaluate the processes that you modelled and also their
outcomes including recommendations for improvements.
Your evaluation report should show evidence of your reading and research and use Harvard
referencing. This is a chance to look back on what you have done and to revisit the key
design and technical decisions you made. Were they the right decisions or would you do
something differently? You should also discuss the lessons you have learnt from the exercise
and how you would use them to implement them in further projects.
Tasks Criteria /Deliverables
Review and
Evaluation
 You have correctly identified the scope of your project
including the specific goals, objectives and tasks
 You have presented the outcome of your project (list
the various tasks that have been completed and the
relevant design principles, theories and tools used to
complete them).
 You have compared your design choices with
researchers and industry practitioners and provided
justification of your decisions.
 You have cited your work properly.
 You have explained the overall project complexity and
clarified how you tackled it using the relevant design
principle, theories and tools.
 You have proposed a suitable methodology to develop
the system.
 You have clarified what would you do differently if you
repeat this project.
 You have clarified the design choices you have made
and how did they affect your results.
 You have discussed the improvement in the areas
which did not go well.
1

Explain your role as a system analyst in the Cheltenham Football Club Information System
project. Explain how did you use the OO approach in designing the system and clarify the
benefits of using the relevant UML diagrams in your design. Remember to address the
advantages and disadvantage of OO paradigm and give examples as appropriate and cite
your work properly. (500 words)
Role of System Analyst –
As a system analysts of the Cheltenham Football Club Information System project the main role to
be performed is that of identification of the main requirements of the infromation system and
making assements so that the required results are obtained. The role of a ssystem analyst is very
important for any type of organization and for all their projects. A system analyst usually deals
with a purpose-built IT solution or a subsystem of a much larger set of programs like an
accounting system. The position deals with what might be termed “mid-range deliverables”. An
“architect” is a much higher pay grade. Architects are systems analysts on steroids. They must
understand the entire enterprise, and they design multi-layered, multi-technology solutions that
operate across functional boundaries. They are aslo resposible for motivating the fellow staffs and
employees of the organization who take part in the developemnt of the proejct along with the
project lead. The system analsyst is also capable of providing sufficient training to the users of the
systems ans also make important anaysis of the requirememnts of the users of the system.
The most important work of a system analyst is done at the start of a development project. That
work requires living with the members who are seeking a technology solution. The system analyst
must understand their business process and see how technology can overcome a problem or seize
an opportunity. Most critically, the system analyst must obtain an agreement with the member on
a set of features and performance standards that they determine will meet their needs. This is, in
the jargon, the “deliverable” — the solution that the project must deliver to the member. The
creating the design of the Cheltenham Football Club Information System project an object
oriented approach was adopted and the procedures of infromation system designed for the club
was handled by this method. The approach helps in the development of the quality of the
products and services delivered by the club.
During the proejct analysis phase the projec the apporcha helped in the resolving very critical
issues that had arisen during the course of the project. The object oriented approach is very useful
for any type of project development as the adoption of this approach would help the designers to
use the classes, objects and instances of the abstraction process that would take place in the
system for the project. The classes based on the object oriented approach has been described in
this section. Hence, this was very important for the development of the project. The method
would help the organization in making easy transition for the changes that are to be made and
also reduce the cost of development at the same time. The problems that the developer comes
across during the development of the project can be very easily identified and overcome with the
help of the object oriented approach.
2

List the key lessons you learned from this project. Clarify what would you do differently if
you repeat it and how you can improve the areas which did not go well. Suggest a suitable
Software Development Methodology to use to develop the system you designed?
Remember to justify your answers (500 words)
During the dev elopement of the project there were various different software
development methodologies that were considered for adoption. However, it was very
important that the most efficient one is selected which would benefit both the
organization and the members of the organizations. This would also help them during
development phase of the project for the organization. It was also learnt that the project
is to be divided in different phases that would help the organization and development
team to focus on one area of the project at a time. There is various area of the project
that can be improved and the object oriented method would be very beneficial in the
improvement of the project and reduction of the possible errors for the system.
The traditional method has been used for the development of the project and the design
and development of different type of diagrams have been done for aiding the
3

development process and for the better understanding of the designing phase of the
system. The state of the project is to be defined for the management of the interaction
process that takes place during the different stages of the project development and the
constraints that appear during the management of communication process that appears
during the project management can be mitigated very easily with the adoption of this
process.
It is recommended that the Agile methodology is that most suitable one for the
development of the project on the information system for the Cheltenham club. The agile
methodology is used for the development as well as risk reduction processes of the
projects. In the Agile Methodology, software is developed in incremental, rapid cycles.
The model combines the incremental and the iterative process that focuses mainly on the
customer satisfaction and the adaptability of the designed product. Iterations for the
process generally occurs in each phase and features are update until the final build is
accepted by the client. The iterations in the in the methodology is used for the increase of
efficiency of the final product and an efficient communication plan for the project can be
maintained. Face to face meetings can take place among the team members of the
organization at each iterations and communication gap is almost eliminated entirely by
this process. The iterations also follow in each of the phases of the project and the coding,
designing and testing phases are also revisited so that most of the errors and eradicated
entirely.
References
Azar, A. T., & Vaidyanathan, S. (Eds.). Chaos modeling and control systems design, 2015,
581. Germany: Springer.
4

Buede, D. M., & Miller, W. D. The engineering design of systems: models and methods.
John Wiley & Sons, 2016.
Endsley, M. R. Designing for situation awareness: An approach to user-centered design.
CRC press, 2016.
Ha, E, "Building design thinking system through the design type of analysis.". in KOREA
SCIENCE & ART FORUM, 20, 2015, 475.
Kan, T., Nguyen, T. D., White, J. C., Malhan, R. K., & Mi, C. C. A new integration method for
an electric vehicle wireless charging system using LCC compensation topology: analysis
and design. IEEE Trans. Power Electron, 2017, 322, 1638-1650.
Montgomery, D. C. Design and analysis of experiments. John wiley & sons, 2017.
Munzner, T. Visualization analysis and design. AK Peters/CRC Press, 2014.
Oinas-Kukkonen, H., & Harjumaa, M. Persuasive systems design: key issues, process
model and system features. In Routledge Handbook of Policy Design (pp. 105-123).
Routledge, 2018.
Pedrycz, W. Granular computing: analysis and design of intelligent systems. CRC press.
2016.
Phillips, C, H Nagle, & A Chakrabortty, Digital control system analysis & design. in . 2015,
p.45.
Romiszowski, A. J. Designing instructional systems: Decision making in course planning
and curriculum design. Routledge, 2016.
Valacich, J., George, J., & Hoffer, J. Essentials of systems analysis and design. Prentice Hall
Press. 2014.
5