ISM4113 - Group Research Project and System Design and Development Project
Group Research Projects
Each group should decide upon a research project topic as soon as possible, develop a short, informal description of the chosen topic that includes an initial development of topical coverage, and e-mail the document to me. The groups should submit research topic proposals as soon as possible so we can make modifications as necessary and finalize the research topics.
Group System Design and Development Project
Each group will utilize Visual Basic (available in the COB Computer Lab and the SAIL, building 79) to develop an information system. The design of the system will be guided by the information presented in the text. A schedule of activities derived from the text chapters is presented below. A complete system documentation file (3 ring binder works well) will be the ultimate result of the project. The system may be submitted either on diskette or CD. The system must be completely functional and self contained (all data files included) when submitted.
The system development project will address a common and popular system design situation: a wholesale and retail manufacturing company that sells primarily to customers who have accounts with the company. The ABC Widget Company is a small company located in Pensacola. John Doe is the owner and chief operating officer. The company produces high quality widgets for retail sales to local companies and wholesale sales to distributors. The company is growing rapidly, and new customers are buying widgets in record numbers. The company is expanding its full line of widgets to include economy and deluxe models in addition to its extensive line of standard widgets.
The company has a relatively good paper based information system in place at present, but it is becoming overwhelmed with new volume. Consequently, a computer based information system is required to support the growth. Mr. Doe has contracted with your consulting company (group) to design, develop, and implement a new information system. Mr. Doe estimates that the company is beginning to experience lost sales due to inability to meet customer service requirements, inadequate inventory control, and inaccurate invoicing and billing. Estimates of losses are as high as $5000 per month in recent months, with the amount increasing by as much as 10% per month due to increased business volume. Customer goodwill is also being lost due to incorrect order fulfillment. The cost of lost goodwill is difficult to measure precisely, but Mr. Doe estimates that future losses will be as high as $3000 per month in the coming months as customers look to other widget suppliers.
For purposes of system design and development, I will play the role of Mr. Doe, the company owner and operator. Each team must schedule a series of interviews with Mr. Doe, beginning Monday, 24 June. The interview topics and conduct will follow the systems analysis information in the text. BE PREPARED for the interview - Mr. Doe is a very busy man and doesn't have time to waste!!!!!
Calendar of Activities
Group System Design and Development Project
Each group must be ready to discuss and review group project development progress on the dates listed below. These reviews are designed to "keep you on track" and to ensure that you are not trying to accomplish too much with your project. The reviews will take place during the regular class hours in the classroom. The order of the review meetings will be determined randomly.
- Chapter 3 - Systems Planning and Selection - documents ready for review on 8, 10 July
- Chapter 4 - Systems Analysis - Requirements Determination - 15, 17 July
- Chapter 5, 6, and 9 - System Requirements: Process Models and Conceptual Models, Database Design - Initial designs - 22, 24 July
- Chapter 8, 10 - System Design, System Implementation - System Project Presentation as scheduled 29, 31 July
- Second Group Peer Reviews due with submission of System Project presentation on 29 or 31 July
Group Peer Evaluations
The first Group Peer Evaluation is due on 17 July. Each group member should complete his/her evaluations, seal them in an envelope and sign his/her name across the back flap, and submit the envelope to his/her group leader with sufficient lead time to have the group leader submit the evaluations to me on the due date. Group leaders: manage your group members!
The second evaluation is due at the close of the group's presentation of their system design and development project. The same procedure should be used to submit the evaluations.
Return to ISM4113 Page