COIT20248 Information Systems Analysis & Design Report 1 Sample
Assessment 1 is an individual assessment. In this assessment, you are assigned tasks which assess your knowledge gained between weeks 1 and 4 about different facets of systems development. All students will have to learn writing a professional business report showing the answers to the required tasks listed below.
Required Tasks
A. Project Planning
During the COIT20248 class, there are ten activities to be performed by the project manager during project planning. List them and briefly explain these activities. Apply these concepts to the case context. Discuss background of project, project scope, problems and opportunities to be addressed, results to be achieved, measures of success.
B. Systems Development Methodologies
Each systems development methodology has its own set of strengths and weaknesses. Explain and discuss three possible systems development methodologies which may be considered for this project, with a comparative table to highlight the main points.
The CEO of the client organisation is ambitious and prefers to develop a new information system with more functionalities (in addition to those mentioned in the business case). However, at this stage the CEO does not have a “complete” knowledge of what functionalities to be included. Recommend one systems development methodology for this project, with convincing justifications. Discuss the main concepts of this methodology.
C. Stakeholders and Communication Plan
Who are the major stakeholders of this project? Provide a communication plan, outlines the communication procedures with major stakeholders.
D. User Requirements
Suggest effective means to identify and collect user requirements of the new system. When collecting information from different users, consider their expectations and cultural backgrounds.
Guide to Learning, Research and Referencing
For the benefits of your learning, you should learn to research and study on quality sources, and to do your own work for the assignment. You can use the Unit learning materials and textbook as a start and then research on primary sources such as peer reviewed academic journal articles or other relevant publication from quality sources.
Please note that all submissions will be checked by relevant platforms including computerised copy detection system. Plagiarism will incur penalties, ranging from deduction of marks to failure in Unit or even exclusion from the University. There are many issues related to the text generated by AI (Artificial Intelligence).
AI is not regarded as a quality source, as it is not a peer reviewed or primary source.
You should keep the drafts of your assignment available for inspection, if requested by teaching staff. The draft documents should demonstrate how your work evolved and the relevant sources you used to support your work. Such documents can show that you have done your own work and showcase your learning experience.
All used sources must be acknowledged by proper in-text references and reference list, with CQU Harvard Referencing Style. Please refer to the following web page for further resources and the link to The Abridged Harvard Referencing Style Guide 2023.
https://my.cqu.edu.au/support?pane=open&content=article&article=/support/ Articles/Academic-Learning-Centre/Referencing
You may seek assistance and guidance from the Tutor of your tutorial group, as the first point of contact. You may also consult your local Lecturer or the Unit Coordinator for further guidance.
Solution
Project Planning
Background
Universe Bookshop is a medium-sized business started by Simon Lee in Australia. At the start of the time, he used to sell books from his garage. He sells books to his friends and families but after some time the business becomes popular. As the store gained recognition, it expanded to serve a wider range of customers. As a result of the introduction of many genres, which showed the market interest, Universe Book Shop grew to become a medium-sized company.
Project scope
Determining the limits of the automated information system constitutes determining the project scope in the context of the University Book Shop. The project scope is defined in the table below:
Problems and Opportunities
Problems
• Bottlenecks result from only one staff member having simultaneous access to critical information.
• Paper-based files mean time-consuming searches and possible loss.
• Reconciling differences between the two forms takes more work.
• The manual maintenance of publisher and customer files results in inefficiencies.
• Sometimes files disappear, which results in delays and lowers client satisfaction.
• There's no efficient way to handle deadlines in the existing system.
• Transactions may be delayed or opportunities lost as a result of this weakness.
• Creating invoices by hand and keeping track of unpaid bills.
Opportunities
• The chance to develop a system that connects the essential components of bookstore transactions.
• Integration of sales, communication channels, and customer connections to provide a smooth process.
• Converting record-keeping from manual to computerized.
• Decreasing search times and increasing consumer and publisher information accessibility.
• Putting in place an automated method for publishers and customers to communicate.
• Adding functionalities for efficient deadline administration.
• Ensuring prompt transaction processing and enhanced customer support.
• Automating the generation of invoices and monitoring unpaid bills.
• Addressing existing inefficiencies to lower consumer complaints and transaction failures.
Expected outcomes
• Streamlined Procedures: Automating critical business procedures, cutting down on the interaction with humans, and expediting transactions in bookstores (Ng et al., 2021).
• Timely transaction policy: The order of books processed is ensured by the use of efficient deadline management systems, which also increases overall operational effectiveness.
• Enhanced customer experience: Accurate order processing, speedier response times, and effective lines of communication all contribute to an improved level of customer satisfaction.
• Efficient record-keeping: Make the switch from manual to automated record-keeping systems, which will guarantee quick access to publisher and customer data ad cut down on search times and mistakes.
Risks and mitigation strategies
Resource palnning
Figure1. Resource chart
Source: Created by author
Quality assurance
• Observance of Industry Guidelines: Make sure the development process complies with industry standards and best practices to provide a stable and dependable system.
• Testing Procedures: Create and carry out comprehensive testing procedures to find and fix errors or inconsistencies in the system.
• Constant Monitoring: To guarantee the system's overall performance, put in place continuous monitoring procedures to spot and correct any deviations from defined quality standards (Ittner and Larcker 2019).
• Peer Reviews: To guarantee code quality, conformity to coding standards, and alignment with project objectives, facilitate cooperative peer reviews.
Systems Development Methodologies
Comparative analysis of three models
Agile methodology is suggested for the CEO’s ambitious goal and nature of project need due to the flexibility, continual improvement, and adaption features.
Stakeholder and communication plan
Communication process
Continual Meetings
• Conduct regular meetings with Simon Lee biweekly to get regular updates on the University store.
• Sales representatives, managers, and employees gather as a team once a month.
Channels of Direct Communication
• A dedicated customer care line for prompt assistance.
• Direct lines of contact for publishers to process orders.
Instructional Sessions
• Staff members and sales reps receive regular training.
• Availability of internet resources for lifelong learning.
Newsletters and Reports
• Monthly newsletters sent to publishers and customers.
• Simon Lee’s progress updates every two weeks.
Mechanisms of Feedback
• Client input through surveys conducted regularly.
• Provide avenues for employees and sales personnel to voice concerns or make suggestions for enhancements.
Online Platforms
• Centralized platforms to handle operational issues for management and employees.
• Publishers may track orders and retrieve pertinent information using a dedicated portal.
User Requirements
Use a multifaceted strategy to efficiently identify and gather user needs for the new system. Complete in-depth surveys and interviews with important parties, such as Simon Lee, managers, salespeople, consumers, and publishers (Chaker et al., 2022). To guarantee inclusion, take into account the users' cultural origins. Conduct focus groups to get a range of viewpoints and expectations. To visually convey system features and accommodate varying learning styles, use mock-ups and prototypes. Engage consumers in feedback sessions regularly to iteratively revise needs. Through the use of an inclusive approach, a thorough knowledge of user demands is ensured, resulting in a system that is compatible with a wide range of expectations and cultural backgrounds.
References
Buttle, F. and Maklan, S., 2019. Customer relationship management: concepts and technologies. Routledge. https://www.taylorfrancis.com/books/mono/10.4324/9781351016551/customer-relationship-management-francis-buttle-stan-maklan
Chaker, N.N., Nowlin, E.L., Pivonka, M.T., Itani, O.S. and Agnihotri, R., 2022. Inside sales social media use and its strategic implications for salesperson-customer digital engagement and performance. Industrial Marketing Management, 100, pp.127-144. https://www.sciencedirect.com/science/article/pii/S0019850121002091
Ittner, C.D. and Larcker, D.F., 2019. Quality strategy, strategic control systems, and organizational performance. Accounting, Organizations and Society, 22(3-4), pp.293-314. https://www.sciencedirect.com/science/article/pii/S0361368296000359
Muhammad, T. and Munir, M., 2023. Network Automation. European Journal of Technology, 7(2), pp.23-42. https://ajpojournals.org/journals/index.php/EJT/article/view/1547
Ng, K.K., Chen, C.H., Lee, C.K., Jiao, J.R. and Yang, Z.X., 2021. A systematic literature review on intelligent automation: Aligning concepts from theory, practice, and future perspectives. Advanced Engineering Informatics, 47, p.101246. https://www.sciencedirect.com/science/article/pii/S147403462100001X
Thesing, T., Feldmann, C. and Burchardt, M., 2021. Agile versus waterfall project management: decision model for selecting the appropriate approach to a project. Procedia Computer Science, 181, pp.746-756. https://iopscience.iop.org/article/10.1088/1757-899X/1169/1/012025/meta