Systems anlysis


Weekly tasks or assignments (Individual or Group Projects) will be due by Monday, and late submissions will be assigned a late penalty in accordance with the late penalty policy found in the syllabus. NOTE: All submission posting times are based on midnight Central Time.

You have been selected to elicit requirements; design; and formulate testing, development, and implementation plans for a software application or system of your choosing. Throughout this course, you will be developing components of the overall specification document that will culminate in the final Key Assignment. Additional information and the deliverables for each Individual Project will be provided in the assignment description for this project.

Project Selection

The first step will be to select an application or a system as the target for developing a comprehensive System Requirements, Design, and Implementation Specification that will have sections from requirements, analysis, high-level, and detail models as well as design, development strategy, testing strategy, and an implementation plan. This project will be used as the basis for each of the assignments throughout the course and should conform to the following guidelines:

  • Nontrivial: The selected software application or system should be a scope that is not too large to develop all of the requirements in a 5.5-week period. A few examples of possible projects include, but are not limited to, the following:
    • An ordering system (such as pizza)
    • An inventory control system (for a small number of parts)
    • A labor tracking or time-card system (for a small company)
    • An online appointment request system
    • An employee emergency contact system
  • Domain knowledge: Students should be familiar enough with the application or system to allow focus on their specification documentation.

Select an enterprise that fits these requirements, and submit your proposal to your instructor before proceeding further with the assignments in the course. Approval should be sought within the first several days of the course. Your instructor will tell you how to submit this proposal and what notification will be given for project approval.


For the assignments in this course, you will be developing an all-inclusive System Requirements, Design, and Implementation Specification. Your first task in this process will be to select an application or system to use as the basis of your projects. You will also create the shell document for the final Key Assignment project deliverable that you will be working on during each Unit. As you proceed through each project phase, you will add content to each section of the final document to gradually complete the final project. Appropriate research should be conducted to support the analysis in your report, and assumptions may be made when necessary.

The project deliverables are as follows:

  • Submit your project proposal to your instructor for approval.
  • System Requirements, Design, and Implementation Specification
    • Use Word
    • Title page
      • Course number and name
      • Project name
      • Your name
      • Date
    • Table of Contents (TOC)
      • Use an autogenerated TOC.
      • This should be on a separate page.
      • This should be a maximum of 3 levels deep.
      • Be sure to update the fields of the TOC so that it is up-to-date before submitting your project.
    • Section Headings (create each heading on a new page with “TBD” as content, except for Week 1)
      • Week 1: System or Application Overview
      • Week 1: Requirements Specification
      • Week 2: System or Application Design
      • Week 3: Test and Quality Assurance Plan
      • Week 4: Development Strategy
      • Week 5: Integration and Deployment Plan
  • Week 1: System or Application Overview
    • Provide a brief description of the system or application's capabilities.
    • Who are the intended users and stakeholders?
    • Who is the project initiator or sponsor?
    • Be sure that this project is approved by the instructor before you proceed.
  • Week 1: Requirements Specification
    • Include the overall goals and objectives of the application or system.
    • Include elicitation methods that are used to gather requirements.
    • Describe functional requirements.
      • Include a short description of the function being supported, a detailed description of the requirements, and how they will be measured during testing.
    • Describe the nonfunctional requirements, also known as attributes of the system addressing areas such as usability, security, and performance.
      • Include a short description of attribute category, a detailed description of the requirements, and how they will be measured during testing.
    • Include assumptions and constraints to frame the scope of the project.
  • Name the document "yourname_IT425_IP1.doc."
    • 4 years ago
    • 20

    Purchase the answer to view it

    • attachment