Requirements Analysis Registration System

Assignment 3 – Requirements

Requirements are central to CIS: in other words, the identification of what's wanted and needed from the intended system. Requirements analysis begins with an (occasionally imprecise) understanding of wants and needs, and it increases in specificity. This exercise will give you practice and feedback on the requirements analysis process.


Suppose that you are to perform the analysis for course registration system. The areas that you will want to focus on include course search, registering and payment for the course. Please consider that a course may have multiple sections, one on-campus, e-live (some on-campus face to face, and some online) and fully on-line. The designed version must be able to function on devices of various sizes and input interfaces such as keyboard, mouse or touch screen.

Some Notes and Hints Before You Begin:

•   It is important that the entire solution is consistent.

Provide requirements, including supporting sketches, for the course search, registration and payment components of the registration system.

Remember that you are setting the requirements: you are not being given whole requirements. Your requirements should be consistent with the scenario above. You may provide additional detail and expand the scope as necessary. For example, you may require intelligence from the system such as advice and checklist popups.

1.  Overview: Provide a one-paragraph overview which introduces the system.

2.  System Users: List and describe the different types of system users (actors) and very briefly how they will use the system.

3.  Functional Requirements: In one single spaced page or less using a 12-point font type with one inch margins, specify key functional requirements to be provided by the system to the various types of users.

4.  Use Cases: Specify the use cases for a single task in tabular format, showing actors, preconditions, actor actions and system responses. Each of these use cases should have 3 steps at a minimum.

Use case Name  
  Step #     Actor     System  
Use case Name  
  Step #     Actor     System  
Alternate Courses:  
Implementation Constraints:  

5.  GUI Sketches: Create GUI sketches for two screens for system. You can use Visio or another design tool of your choice.

6.  Non-Functional Requirements: Specify what you consider the two most important non- functional requirements. Describe your choices briefly and explain why you have considered these most important.

7.  Organizing Requirements: Organizing by Use Case, GUI, or Functional Requirements are three of many options available when systemizing requirements. Describe and contrast two of these three ways in which the requirements for your system could be organized. Give specific advantages and disadvantages within the context of your system scenario.



•     Do not underestimate the time required to write a clear overview that is short enough to be readable, yet long enough to convey what the system does, structured appropriately.

•     You may want to come back to this section at the end to make sure it is consistent with the rest of your solution.

Functional Requirements

•     Make sure that you describe the major functionality.  Enumerate and describe your functions systematically.

•   Make sure to understand the difference between functional & non-functional requirements.

•     You may want to do some outside research to see relevant examples of how functional requirements are defined for systems.

Use Case

•     The use case name, primary actor, precondition, and action/system response steps should be shown at minimum.

GUI Sketches

•     There is no need for elaborate GUI’s here. Decide what information should be contained in each screen and draw rough mockup sketches. Use single rectangles for GUI windows, specify

prompts to users, and use rectangles for text fields where users enter data. Indicate system output text to users as a series of x's.

Non-Functional Requirements

•   Make sure to understand the difference between functional & non-functional requirements.

•     You may want to do some outside research to see relevant examples of how non-functional requirements are defined for systems.

Organizing Your Submission

You will want to organize your response as a paper write-up. The following are suggestions to a clearly organized response.

•   Make sure to include your name in your assignment solution.

•     For diagrams, make sure to paste them into your solution within the appropriate section and that they are legible.

o  Hand-drawn and scanned diagrams are not accepted, I want you to practice using modern design tools.

•     Make sure to use proper referencing in your paper. I suggest is APA format, but other formats are fine as long as it’s clear in distinguishing your work from work of others in your response, be mindful of plagiarism rules.

o  Make sure to include a reference page, but also show how these references are used within your response.

•   Include your last name in the file name of the assignment.

o  (Example: ZeffronSmitz_Assignment3.docx)

Requirements Analysis Registration System

  • Order

  • Payment

  • Processing

  • Delivery

Validation error occured. Please enter the fields and submit it again.
Thank You ! Your email has been delivered.