You are on page 1of 6

BA 353/ ACCY 353 – Information Systems Analysis and Design

Spring 2007

Group Project Systems Development

Throughout the semester, you will design an information system for a specific usage.
You can either choose a system from three project samples listed below, or come up with
your own idea. The objective is to challenge yourselves, while staying realistic.

Overview of deliverables
Due Date Deliverable Points
2/12 1. Project Proposal 10
2/19 2. Requirements 5
2/28 3. Data Flow Diagram 15
3/7 4. Entity Relationship Diagram 10
3/7, 3/12 5. Presentation Part I 15
4/4 6. Acquisition Strategy 5
4/18 7. User Interface Design 15
4/25 8. Physical ERD 5
4/30 9. Conversion Strategy 5
4/30, 5/2 10. Presentation Part II 10
Day of Final
11. Final Project Report 5 + 10
Exam (TBA)
Total 1101

1. Project Proposal (10 points)

The main purpose of the proposal is to give a general description of what you plan to do
as your project. You should be able to describe in simple terms the ‘big picture’ behind
what you envision to complete as a project by the end of this term. It is not necessary to
go into the details of the project right now – that vision you will gradually evolve over
time. The proposal should be at most 5 pages long, written in 12-point font size and
double-spaced.

There should be a separate cover page for the proposal that will have the names of all the
group members, the class (BA 353), and the date on which the proposal is submitted.
Try to be conservative in your model – do not go into details that might make the system
overly complicated, since the purpose of the project is to reinforce the basic ideas behind
systems analysis and design, not build robust commercial-grade applications.

The proposal includes a system request (Figure 2-2, p.35), analyzes feasibility (Figure
2-11, p. 50), and estimates project size (p. 64-70) In addition, you may also need to
consider the following questions (in no particular order):
1
100 points are needed for full credit. Up to 10 extra points will be awarded for improvements to earlier
deliverables that are included (and described) in the final report.

Page 1 of 6
1. What are some of the things your system will not address (essentially,
defining the boundary)?
2. What are the main interactions of the system with its environment (inputs and
outputs)?
3. Who will be the users of this system?
4. What kind of data is to be stored in the database?

2. Requirements (5 points)

Describe functional and nonfunctional requirements, referring to Chapter 4 (in


particular Figures 4-1 and 4-2, pp.104/105)

3. Data Flow Diagram (15 points)

Your Data Flow Diagram should include three parts:


1. Context diagram
2. Level 0 diagram
3. Level 1 diagram

4. Entity Relationship Diagra m (10 points)

Prepare an ER Diagram for your project. Note: You are required to use computer-aided
software engineering (CASE) tools to draw all your diagrams. In this class, you will learn
how to use Microsoft Visio.

5. Project Presentation, Part I (15 points)

In your presentation (30 min or less), please summarize your deliverables so far (Project
Proposal, Requirements, DFD, and ERD). Be prepared to answer questions from the
audience (incl. your instructor), such as:

1. Who sponsors the system?


2. What are the drivers behind the proposed system? Why do we need the system?
How will the system create value for the company?
3. Who will use the system? Who will be affected by the system?
4. What will be the economic value of the system (economic feasibility)
5. Is the system technically feasible?
6. How do you ensure organizational feasibility?
7. How big is the system? (How did you determine size?)
8. How long will it take to build the system?
9. Who will be on the project team? (Internal/external staff? Qualifications?)
10. What are the system requirements? How were they determined?
11. How is data processed in your system? (explain the DFD)
12. What data is stored and where? (DFD, ERD)
13. What business rules are included in the ERD?
14. What are the next steps to go forward?

Page 2 of 6
6. Acquisition Strategy (5 points)

Explain your planned acquisition strategy, referring to Chapter 8, Figure 8-4, p. 262.
Include an explanation of the reasons to choose the particular strategy, describing issues
related to business needs, in-house experience, project and project management skills,
and time frame. (3 pages max, written in 12-point font and double-spaced).

7. User Interface Design (15 points)

The User Interface Design deliverable includes three parts:


1. Key use scenarios for the system (what kinds of users will be using the system
and how will they interact with the system?) (Figure 10-6, p. 316)
2. Interface structure diagram (ISD) (Figure 10-7, p. 318)
3. Storyboard (Figure 10-8, p. 322) or HTML prototype

8. Physical ERD (5 points)

Refer to p. 410-413. Include an estimation of the needed storage size, referring to pp.
424-426

9. Conversion Strategy (5 points)

Describe your planned conversion strategy (Ch. 14). Include an explanation of the
reasons to choose the particular strategy and describe the cost, time, and risks involved
with the chosen strategy (3 pages max, written in 12-point font and double-spaced).

10. Project Presentation, Part II (10 points)

- To refresh the memories of your audience, please, provide a short summary of


the content of your first presentation (focus on the purpose of your system,
and on the key factors that you took into consideration during the initial
phases of your project).
- Discuss the new deliverables: User interface, physical ERD, acquisition and
conversion strategy.
- For each deliverable, please tell us what you did or plan to do, and why. For
example, please tell us what decisions and trade-offs you made during user
interface design.
- In addition, please describe any changes that you made to the previous
concept of the system, and explain why you made the changes.

Page 3 of 6
11. Final Project Report (5 points, plus 10 extra points)

The report should include everything that you have done so far in the project:

1. Project Proposal
2. Requirements
3. Data Flow Diagram
4. ER Diagram
5. Acquisition Strategy
6. User interface design
7. Physical ER Diagram
8. Conversion Strategy
9. Brief conclusion of the project (1 page)
10. Appendix
a. Handouts of Presentations I and II
b. Change report

Up to ten extra points will be awarded for improvements to earlier deliverables that are
included in the final report. Please, describe the changes in adequate detail either together
with the respective deliverables or separately in a change report to be included in an
appendix. The objective of this arrangement is to encourage the groups to keep improving
the system deliverables after their original due date and grading by the instructor.

Sample Project Descriptions

Remember to challenge yourselves, while staying realistic.

1. Rental Car System

Design an information system, which will facilitate the functioning of a "typical" Rental
Car store. Assume you carry cars of several "Types" such as economy, mid-size, luxury,
van, SUV, pickup etc. Each type of car should have a different rental fee per
day. Rental fee depends on number of days, mileage, insurance, and use of gas. Every
hour late should be charged $10 till the late fee equals one-day rent. The system should
have the following functionalities:

(i) Reservation: The system should be equipped to answer Customer's inquiries about
the availability and rental fee of various "types" of cars for certain dates in the
future. When the customer makes a decision about the "Type" of car and the
Dates, the system should be able to "Reserve" or "Earmark" the requested type of
car for requested dates. The customer should be given a "Confirmation Number".
(ii) Pick Up: The system should be able to process a Car Pick Up. Customer walks
in and supplies either the confirmation number, or name. The system should pull
up all the reservation information about this customer. The customer is then

Page 4 of 6
asked to supply a credit card and drivers' license. When these two things are
verified, a specific car is assigned. Mileage of the assigned car is noted. The
customer is also asked if they want to buy insurance.
(iii) Return: The system should be able to process a return. The system should record
the date, time, mileage and gas. Depending on these parameters, the system
should calculate the final rental amount.
(iv) Reports: The system should provide the management with useful reports and
queries to help them run their business better.

2. Video Rental System:

Design an information system, which will facilitate the functioning of a "Typical" Video
Rental store. You carry videos of various types such as Drama, Horror, Comedy, Action
etc. (no adult). Rental fee depends on "New" or "Old". You typically carry several
copies of the same title. The system should have the following functionalities:

(i) Membership: The system should be able to make new members, modify data
about existing members and delete members. Relevant data about the customer is
kept on record.
(ii) Answer Customer Queries: The system should be able to answer customer queries
regarding the availability, rating, and rental fee of videos based on Title, Actors or
Actresses, Directors etc.
(iii) Rent Out: The system should be able to process rentals. Any previous balances
(late fee from previous returns) should be paid off before new rentals are allowed.
The Rating of the Video should be matched with the age of the Customer. Fee for
new rentals should be collected. The system should keep track of how many
times a particular copy of a video has been rented out so that it can be retired after
25 rentals.
(iv) Return: The system should be able to process returns. Based on the return date,
late fee if any should be assessed.
(v) Reports: The system should provide the management with useful reports and
queries to help them run their business better.

3. Sales System for a Wholesaler:

Design an information system, which will facilitate the functioning of a "Typical"


wholesale operation. You may assume any product, such as books, furniture, clothing
etc. You basically order and receive products from manufacturers and you take orders
from and ship to your customers who are "retail" businesses. The system should have the
following functionalities:

(i) Maintain Customer and Supplier Data.

Page 5 of 6
(ii) Order Entry: The system should be able to answer customer's queries about the
price and availability of various products. Once the customer decides their order,
the order should be taken and an estimated total amount and expected delivery
date computed.
(iii) Shipping and Packing Slip: Shipping of each order should be processed and a
packing slip generated for each shipment. Quantities shipped should be
subtracted from Inventory records. An invoice should also be generated.
(iv) Place Orders: For products running low, an order should be placed with your
suppliers. An expected date of "receipt of products" and expected quantity should
be recorded against the products ordered. This information will facilitate the
Order Entry system in providing the customer with information on back orders.
(v) Receiving: When goods arrive, they should be processed. They should be
confirmed against order placed and the inventory should be adjus ted to account
for the increase in quantity.
(vi) Reports: Meaningful reports and queries should be generated to help
management run their business better.

4. Your own system:

If you would like to design your own system, one suggestion is to start with something
that is related to your daily lives, such as a system to improve administration at the
University of Illinois, College of Business, your dorm, gym, or even your favorite bar or
coffee-shop. You are encouraged to talk to potential users of the system, in particular
during planning and analysis phases.

Page 6 of 6

You might also like