Assignment 1 – System Categories & System Analysis

The two parts of this assignment will be evaluated separately.  They will contribute equally to your homework grade this week.  Please note the page limitations; however, you may include as many appendices as you wish but these will be read only on an as-needed basis. For all homework assignments, be aware of deadlines, the grading criteria (the evaluation matrix in “Syllabus/Grading Criteria for Homework”), and plagiarism rules.

Part I

The purpose of this exercise is for you to think through major information system categories.

Describe four different types of realistic business information systems as discussed in Module 1 (“Types of Business Information Systems” Section) or in your textbook on pp.44-46.   You may respond by writing in the table below.  But do not allow this format to limit you: if you need more space to make yourself clear, use reference numbers (1), (2) etc. in the table locations, and expand on each below the table on the next page.  You will want to do outside research to gain understanding of these types of systems through examples.  Use these references to support your points.

For four systems selected from (b) through (h), specify ii through v in the table or in a page or less of 12-point type.

1. The type of the system (already provided for you in the table)
2. Its purpose

• The typical user(s) of the system and their means of interacting with it

1. The input data used by the system
2. The system’s output

In selecting the systems to describe, give preference to those systems that are customer focused and user-oriented. E.g., avoid embedded systems, operating systems, utility systems such as a registry repair systems, etc., where either the user is either absent or understanding of the internal workings of the system is required.

Notes/Hints:

• One way to approach to some of these parts is to think about a midsize or large business that you know, and try to identify the type of information system it uses. Do some research around these businesses and the systems they use.
• Make sure to clearly differentiate the systems. For example we want to see that you understand the key differences between executive information systems and decision support systems, avoid overlaps.
• A good way to work references into your response is to show example systems through examples on the second page.
• You won’t be using XML tools on this assignment, “Utilization of resources or UML tools” is based on specifically on utilization of resources.

Important Note:

• Seven systems are listed in the table on the following page; you are to choose just four of these systems in your response.

• See Part II on next page

Part II

The purpose of this exercise is to have you think about the major parts of system analysis, and thereby to help you appreciate what issues system analysis needs to address.   Use the “basic” systems analysis methodology given in Module 1 (Section “System Analysis Methodology and Software Engineering”), and apply systems analysis to the following task.

ExamProctors, a company which proctors final exams on-site wants to provide web based services. This would enable universities and schools to provide their students (test takers) capability to sign up as well as to have their exams proctored and monitored remotely through ExamProctors.  ExamProctors would need to partner with various LMS (Learning Management Systems) as the exams would be completed by the test takers within the LMS itself.  ExamProctors would utilize cameras and microphones to both verify the test taker’s identity and to monitor the exam.  ExamProctors should run in two different configurations, both “record and review” mode as well as “live” mode.  ExamProctors would need to run on both traditional and mobile environments.

Use the basic methodology as follows, in a maximum of four single space pages of 12-point type not including appendices, and provide the following.

1. Mission Statement
2. Functional System Requirements
3. System-Level Use Case
4. System-Level Quality System Requirements
5. System-Level Constraints

The course will examine these topics in detail during the next several weeks.  Your write-up for this exercise is not expected to be formal or in complete detail.

Notes/Hints:

• Start by reviewing examples given in Module I. See QuickQuote (in the “Example of System Analysis Methodology” section) and ElecPak (in the “Example of Systems Engineering” section).
• The mission statement must give a high level context and scope for the system. A good place to start is to research mission statements of systems that you use.  Think about key functionality and who the main users are.  The mission statement should be about a paragraph in length.
• Functional, quality system requirements and system level constraints should be written in short paragraphs, each discussing one topic only.
• Be sure that you understand the difference between a functional requirement (step 2), quality requirement (step 4) and a system constraints (step 5).
  • The functional requirements should describe only what the system does – not design decisions for implementing these requirements.
  • Design decisions the how are non-functional quality requirements and constraints, for example: using a particular laptop, programming language, GUI layouts, or encryption method should be documented as constraints (step 5) and not as functional requirements.
• System-level use case may repackage information contained in the functional requirements in a different format: a scenario-like sequence of user actions and system responses. It is common to have one use case for each overall functional system operation.
• Use consistent terminology while describing similar or the same things (e.g., you would avoid using the term “students” in one place and test takers or “user” in another to describe the same person).
• Be sure to spend time to review your response iteratively going back to previous sections. For example, once you complete system requirements, use cases, and constraints, make sure that they are consistent and that the Mission Statement provides a top level overview.
• A good way to work references into your response is to show example systems through examples within an appendices section.
• UML tools are not needed for this solution.

Organizing Your Response

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

• Include a title page, and a table of contents.
  • Although obvious, make sure to include your name in your assignment solution.
• If you want to include some of the elements from the assignment directions and characteristics, organize these in the introduction section, but only include sections which you feel add to the clarity of your response.
• Make sure to use proper headings and sub-headings in organizing your response. For example, this particular assignment has two parts, with multiple sub-sections.
• Make sure to use proper referencing in your paper. We 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.
  • 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.
  • (Example: SmithMichael_CS682Assignment1.docx)