C-S 341 Software Engineering Spring 2008 Project Description A Simple Li rar! "anagement S!

stem
# jecti$e: For this project a simple library management system will be created. Description of t%e pro lem: The simple library management system will support the process of a small public library. There are several types of users who must login in order to use the system: Administrator: An administrator can create, modify or delete the accounts for everybody in the system including other administrators. All administrators will have equal privileges. Borrower: A borrower can chec or update his!her personal information, search an item by title, author, or subject , chec out the item by him!herself, pay the fines if there is any, and place an item on hold if it has been chec ed out by others. "ibrarian: A librarian can do all the functions a borrower is able to do. #n addition, a librarian can add or delete an item from the library, and change the information about an item in the library system.

The following minimal set of functionalities must be implemented: $rovisions to add, search, remove, modify, view and print different types of users. $rovisions to add, search, remove, modify, view and print an item information. The system should be able to generate the return date and billing information if past due date. The borrower should be able to pay the fines if there is any. A graphical user interface must be developed for this software. The interface must consist of multiple screens for different tas s. For e%ample, there should be a welcome screen to start with which displays the various functionalities of the software. The number of screens, the screen layout, the type of information to be displayed etc. all depend on your design. &ou must implement all the functionalities mentioned above. &ou can associate a database with your product, if you wish' however, it is not required.

Project Deli$era les: )uring the life cycle of this project, the following documents must be delivered. )eliverable )ocument ( )ocument )ocument 3 )ocument 7 )ocument 6 )ocument 2 )ocument : )ocument . )escription $roduct +verview and Assumptions Functional 1equirements *ar (, -, )ue )ate Feb. (-, /Tuesday0 Feb. -2, /Tuesday0 April. (, /Tuesday0 April. ., /Tuesday0 April -8, /Tuesday0 *ay 2, /Tuesday0 *ay ., /Thursday0 *ay ., /Thursday0 -,,. -,,. -,,. -,,. -,,. -,,. -,,. -,,.

45# requirements, initial 45# )esign (6 and 45# demo Architectural )esign /5*" )iagrams0 (, )etailed ++ design 9lides of project presentation (6 6

$roject demo and well;commented (6 source code 5ser manual or online help system (,

This is a team project for this course. <ach team consists of -;3 students. The project wor involves developing software /program, documents, user manual etc.0 for a given problem. The students should form the teams by themselves. #n e%ceptional situations, the instructor will help in forming the teams. #t is highly recommended to join with students who have different bac ground and interests. By this way, a student will learn more on technical aspects as well as s ills to wor in different environments. 4roup wor itself is an important software engineering s ill. +nce joined in a team, no student is allowed to change teams until the project is completely finished /commitment=0. <ach member in a team will get the same mar for the project. #n order to avoid conflicts on wor assignments, the team members are e%pected to equally contribute to the project. #n addition, e$er! &oc'ment m'st e accompanie& ! a signat're page t%at confirms t%at all mem ers of t%e team agree to accept t%e same mar( gi$en to t%e team . 9ubmissions without the signature page will not be evaluated and consequently, the team may lose mar s for that submission. The team members must meet regularly' all discussions must be recorded and submitted to the instructor. #n addition to the above deliverables, the following documents must also be submitted' these documents will be evaluated to chec for equal contribution from each team

member. >owever, these documents will not carry any mar towards the grade. Failure to submit any of these documents will affect the grades of all members in the team. A project plan. The purpose of this document is to develop a detailed plan for the project and assign wor for each team member. *eeting logs. <ach team is e%pected to meet at least a couple of times before submitting a deliverable. The minutes of each meeting /called the meeting log0 must be recorded in a predefined format and must be submitted along with the deliverables. 9ignature pages. <ach deliverable must accompany a signature page. This page must contain the team identification, the names of all team members, the identification of the deliverable, the date of submission and the following sentence: ?@e, the team members, agree to share the mar for this document equally among ourselves.? The signature must be signed by all the team members. The purpose of this signature page is to avoid potential conflicts in wor ;sharing, if they occur. Team member evaluation report. This document must be submitted at the end of the project separately by each team member. <ach member must evaluate the contribution made by every other member in the team. This document must be submitted along with the project plan /the project plan must be submitted earlier in the course and will be returned bac to the team0. The instructor will evaluate the contribution made by each team member. #t is e%pected to have a close match between the project plan and the team member evaluations, even though in some cases there will be some changes in the wor assignment during the development of the project.

)"P#*+A,+- All &oc'ments m'st e t!pe&. ,o %an&-written &oc'ments will e accepte&.