The individual project paper consists of a comprehensive analysis, evaluation, and design of an information system for an organization using the Systems Development Life Cycle (SDLC). This paper, or better, collection of papers, solves a problem or helps realize an opportunity. The simplest way to think about this is that you are going shopping. First you need to know what you want, you go compare products, you make a decision and buy the product, you go home and use the product.
You will pick a local company for analysis. You do not necessarily need to have contact with the company or organization, but you should be able to accurately understand the business case and the real or proposed information systems which support the business case. I recommend you think “small business” or a start up or a family business that’s looking to automate/update part of the business. Consider shopping for an accounting system, a customer management system, a project management application, an inventory management system, a database, or an app specifically suited to running the business. What could you do for that smoothie shop down the street that writes down your order on a pad of paper and only takes cash?
Because this is more than just you, what you do must be described and communicated to the other stakeholders.
The first step is to plan. The plan is already somewhat determined in that you will first plan (and characterize the objectives).
Then step 2, analyze per your system requirements and make a selection/solution from various alternatives or options (it’s like going shopping).
Then step 3, you will present your solution as a system design as it will work for the business (apply the solution and describe how that would look on the business).
Again:
Step 1 (Appendix 1: The Plan) – The plan starts by answering three questions:
What kind and scope of information system would you need to promote the company’s need? Whatever you do would require an information system to support it.
What are the system components?
What purpose will they serve?
Then describe the steps you are taking as part of the SDLC. For example: Step one is important because it defines the need the project will fulfill. Step one will also outline what is going to be done in Step 2 (analysis and requirements) and Step 3 (the systems design). Finish the plan by explaining how all the documents created in the steps 1-3 will culminate in the final report.
Step 2 (Appendix 2: Analysis and Requirements) – Then, what are the requirements or characteristics of the systems that would be part of a successful system? This step is where you determine what questions to ask and then sort and organize the answers. For example: Based on the need defined in step 1, step 2 should clarify what is required (the requirements) of a representative information system. Find information about at least three applications that could fill the need. Compare the systems per the requirements and analyze the data available. Based on the analysis, pick an application you determined best fills the need. The web site www.capterra.com is built to analyze and select applications across a wide range of domains. Capterra also provides comparison tables which can be used as the basis for the analysis and included in the paper.
Step 3 (Systems Design) – The last step is the final design. What pieces now make up the design (which may be a combination of “off the shelf” applications)? How does the design respond to the requirements you established in the second step? Are all requirements met? Or, did some requirements get deleted or new ones created? How does the final design fit with the original components and purpose you envisioned at the start? Answer these questions by showing how the newly selected system will be applied within the company or situation you are representing. Show screenshots of the input screens and reports from the chosen application and explain how they fit the need.
Alternatively, pick yourself as the focus. Step 1 – What kind and scope of information system would you need to promote a personal brand or start-up company? Whatever you do would need an information system to support it. What are those components and what purpose will they serve? Then, what are the requirements or characteristics of the systems that would be part of a successful system? Step 2 – This step is where you determine what questions to ask and sort and organize the answers. Step 3 – The last step is the final design. What pieces now make up the design (which may be a combination of “off the shelf” applications)? How does the design respond to the requirements you established in the second step? Are all requirements met? Or, did some requirements get deleted or new ones created? How does the final design fit with the original components and purpose you envisioned at the start?
Along the way through this process, find and develop sources of information that support both your project content and the process. If you are creating a personal brand, then include sources that speak to personal branding and what frameworks must be realized to create a personal brand. There may be more than one way this is done. Then, present the alternatives and why you chose the one you did. Whatever topic you choose, include information about the topic and the alternatives available. The references for the paper should be a combination of sources about your topic and about the process (SDLC) you are developing.
Appendix 1 – Planning
Submit the initial planning document. This document should include the project’s goal, purpose, and alternatives. Also, present basic assumptions and anticipated milestones for completing parts 2 and 3. See the LFA guide for specifics on defining the goal, purpose, and alternatives.
Appendix 2- Analysis and requirements
Present step two in the SDLC. This constitutes a thorough evaluation of the alternatives presented in step 1, planning. See the LFA guide for more information on alternatives.
A business analyst (BA) would call this step an “options analysis”. The BA is analyzes the options or alternatives available. The following link provides a short three-step process of identify, analyze, select. Your analysis will be more of a product comparison.
Appendix 3 – System Deign
The third phase describes, in detail, the necessary specifications, features and operations that will satisfy the functional requirements of the proposed system
