Assignment 1 Term 2, 2013
The purpose of this assignment is to provide you with experience in some basic tasks of a systems analyst. This is given in the context of an imaginary case study. In your second assignment, you will join with another class student forming a two-person group to develop your case study, working on additional analysis tasks.
The case study scenario given below is to form the basis for your assignment. However, it is expected that you use your imagination to add more detail to the case study to make it your own unique project. It is expected that you will submit your own individual work for this assignment. Begin by reading the case study and then conduct some research of your own and decide upon the details of a project for an imagined small business. You can choose any kind of business as long as it fits in with the partial specifications given in the case study. It is expected that no two students’ assignments will be the same, so make sure that your business has unique characteristics such as name and logo. Though it is expected that some of your requirements will be similar to others, it is also expected that each student will have at least one unique requirement in their project that differs from those of your classmates.
You have been employed as an analyst for a small start up company specialising in web based database systems using php/mysql. Your colleague has visited a potential client for a briefing on a new project. Details are unclear at this stage, however you have been asked to prepare a draft scope document as a starting point. Your boss intends to develop a budget based on the information in your document and then show the scope document to the client at their next meeting. You haven’t time to wait for more details, so you have been asked to make assumptions where necessary. These can be explored with the client at the next meeting.
Your colleague met with the manager of the business and gathered the following information. There are at least 80 frequent-user customers of the business who pay an annual loyalty fee. When the fees are due for renewal, the business sends a renewal notice to the customer with an invoice requesting payment. If fees remain unpaid, the customer status is changed to ‘Inactive’, otherwise, the status remains as ‘Active’. After a customer has belonged to the business for more than ten years, their status is changed to ‘Life Member’ and they no longer have to pay the annual fee. Customers with an active loyalty status are given a 10% discount on all items.
Currently, the business uses a paper based system to keep track of customers’ addresses, telephone numbers – home, work and mobile. It is hoped in the future that the new system will be able to have customers access it remotely to update their personal details after validating themselves using their customer number and a password.
The accountant would like to be able to print reports that list all loyalty customers and their current status. When fees are paid, the accountant would like to be able to log in to the system and update customer status. It is thought this will be done based on a query to pull up details for a customer, and then an option available to update the details as required. The business offers a range of items for sale that could be part of the new system. There is an inventory of items available. Each item will have a status such as ‘in-stock’, ‘on-order’ or ‘out-of-stock’. There will be an on line ordering system, so customers can order items online by logging in and filling out an online order form. The accountant would like to add online payment methods to cash payments made directly over the counter.
The business would also like to engage in charitable work for the local community and so, a fundraising page on the website would be good to attract sponsors and raise funds for supported charities. It is suggested that potential sponsors and also customers of the business who would like to take part should be able to sign up and access this page to make their contributions. Another function of the system is to display business newsletters.
Your colleague forgot to ask whether there were different levels of access to the system for employees, depending on their role in the business, although your boss thinks this may be the case. The schedule is to be displayed for both customers and employees to view when they log in to the system.
You are to create a draft scope document for the project described above. Your document must include a title page with your name as author, project name, client name, date and a version control table stating this as draft 1. Your draft scope document should be presented as a formal professional document.
The document should contain the following:
A name and logo for your virtual business, a paragraph describing the objectives and purpose of your business and a paragraph indicating how the new system will be used to improve processes in the business.
A list of the major stakeholders that may be involved in this project.
For two different types of potential users of the proposed system, a description of each user profile and an example scenario of how they would use the new system (giving step by step details).
A paragraph entitled ‘Scope and Constraints’ in which you describe at least 4 high level broad objectives of the project. Specify also at least one feature that will be outside the scope of the project (e.g. onsite testing, conversion of old data into new system, training.)
A detailed list of requirements of the new system, including a unique REQUIREMENT ID (use numbers and/or letters) for each requirement and present these in a table with ID in the first column and requirement description in the second column. In particular, focus on the online ordering system, the fees for invoicing and collection, and treasurer`s reports.
Organise your table to present two categories of requirements – functional requirements and non-functional requirements.
You must have at least 10 very specific functional requirements*. Don’t summarise: for example, don’t say ‘print reports’, but give details on each report separately as a separate individually numbered requirement.
*ITECH 6101 students must have at least 15 functional requirements and at least 3 non-functional requirements for your system. These might relate to features such as: performance, behaviour, quality, look and feel.
Sketches of a high level draft concept of the user interface. At this stage, your design is concerned with what content would be on each screen, and how it would be presented rather than detailed layout. State whether you will use menus, buttons or input fields. At least one screen should contain input fields that require automatic validation. Clearly state what validation is required. Include a sketch and detailed description of at least 3 screens.
Due Date & Weighting:
Refer to the Course Description for these details and for other items relevant to assignment tasks.
You are required to submit your scope document including screen dumps of the required diagrams/charts on/before the due date. This file is to be uploaded to Moodle. Your tutor may also require a hard copy.