b tech cse project sommerville

7/30/2019 b Tech Cse Project Sommerville

1/7

http://cse.stfx.ca/~mlin/cs485/assignments/project.htm

CSCI-485 Project

A major component of this course is the design and implementation of a completesoftware system. This project is a single software product that is developed over thecourse of the term. Although the final software product is important, the emphasis of thisactivity is the software development lifecycle.

The following is a brief description of the project. As most initial descriptions of softwaresystems, the specification for the software is ambiguous. Your job is to develop thesystem following the full software development lifecycle from requirements analysis

through product delivery.

A Meeting Scheduler System (MSS)

The department would like to have a meeting scheduler system to schedule various typesof meetings. Examples of such meetings are departmental meetings, undergraduate or graduate thesis presentation. The MSS should be able to find a time slot suitable for all

the attendees who must attend the meeting and be able to accommodate other potentialattendees (for example, in a time slot when many students can attend). The systemshould be easy to use. MSS can be accessed via a web interface. The MSS should allowsome users (e.g., the departmental Administrative Assistant or meeting organizers) tocreate meetings and send communications and/or confirmation regarding the schedules of the meetings. The users can login to MSS or may be brought to the web interface of MSS

by clicking a link sent by the organizer of the meeting via MSS. The user can specifytheir preference and constraints for the meeting time. The MSS should allow the admin tointegrate the course schedules of the professors and the students when needed. The MSSshould also allow users to specify a number of options for different types of meetings.

Other possible projects:

Departmental Student Tracking System (STS)
http://cse.stfx.ca/~mlin/cs485/assignments/project.htmhttp://cse.stfx.ca/~mlin/cs485/assignments/project.htm


2/7

The department would like to keep track of all students who have graduated from our department. The STS should keep track of contact information, what the student is doingafter graduation (i.e., working for a company, graduate studies, etc..), etc. The STS

should be easy to use and there are many tasks that it should make automatically. For example, there should be a web interface to the system that allows students to updatetheir contact information, employment status, etc.. The system should also allow for theautomatic distribution of news/announcements/newsletters to all the students registered inthe database, etc. Obviously, the STS must be secure and thus students will need a

password to access the system. There will also be different types of users. For example,the STS will allow some users (e.g., Rhonda, the departmental Administrative Assistant)to send communications regarding events, etc.. to all the students in the database. TheSTS should also allow some users to specify a number of options, preferences, and/or actions to be automatically taken by the system.

Departmental Electronic Bulletin Board (EBB)

The department would like to have a nice way to make announcements regardingupcoming events, etc... to all students and members of the department. We now have a

physical bulletin board in the Annex that will be used for posting such announcements.But we would also like to have an electronic version (web-based) of such board so thatstudents/faculty members do not have to physically come to see the board in the Annex toget information/updates. The EBB should be easy to use and there are many tasks that itshould make automatically. For example, suppose there is an upcoming talk announcedon the board. After the talk is over (i.e., the day after the talk), the EBB mustautomatically remove the announcement from the board. Also, if any changes are madeto any announcements (i.e., a room change), the EBB should automatically update theannouncement and perhaps e-mail everyone to let them know of the change. Obviously,the EBB must be secure and thus users will need a password to access the system. Therewill also be different types of users. For example, the EBB will allow some users (e.g.,Rhonda, the departmental Administrative Assistant) to post announcements on the board.Other users (e.g., students in the department or faculty members) should be allowed tosubmit announcements through the system, but the announcements will be first reviewed

by another user (e.g., Rhonda) before posting on the board. The STS should also allowsome users to specify a number of options, preferences, and/or actions to beautomatically taken by the system.


3/7

Team Structure

Each team must consist of 4 people. The team will consist of team members and a team

leader. The team will choose its own team leader (the team leader will receive a 5% extracredit). All team members share responsibility for the final product demonstration. Teamswill be given some class time to meet and to discuss issues with the instructor, but eachteam should arrange its own schedule for completing and submitting the projectdeliverables on time.

Responsibilities of the team leader:

Schedule meetings, maintain weekly schedule and record meeting minutesComplete the weekly status report of the project and update the project websiteKeep a log of all e-mail communications between team members. All e-mailcorrespondence should be e-mailed to the entire team, even if directed at a particular individual. Also, any conversations about the project between the team leader and anindividual team member or instructor should be communicated to other team membersvia e-mail.Resolve problems between team members by personal action or by involving theinstructor

Responsibilities of a team member:

Be a productive member of the teamAttend all team meetings and participate actively. Notify your team members if youcannot attend a meeting due to illness or other reason.In each meeting, report your progress since last meeting. Take initiative and suggest whatshould be done.Review all meeting minutesIf for whatever reason your contribution falls short of that of other team members,negotiate to take greater work share in the subsequent deliverable(s)Take any personal conflicts with other team members to the team leader Complete all assigned tasks to the best of your ability and in a timely and professionalmanner Complete the weekly report and work log sheet. Update the corresponding web page thatcan be accessed via the project website.


4/7

NOTE: All team members are equally responsible for all aspects of the project.Distribution of the workload has to be agreed upon by all members.

Phases and Deliverables

The following phases will be conducted as part of the software development process. A project deliverable will be submitted to me at the end of each phase. No late deliverableswill be accepted.

1Project Plan5%Jan. 19

2Requirement25%Feb. 13

3Design25%Mar. 9

4Development &Testing25%Apr. 2

5Delivery10%Apr. 9


5/7

1. After forming the team and deciding the project, your first task is to develop a project plan. The deliverable for this phase is the Project Plan document. Note that youshould regularly revise this document, as some parts, such as the project schedule, willchange frequently. Thus, in order to simplify revisions, you should organize this

document into separate sections that can be individually replaced as the plan evolves.(5%)

2. The requirement specification phase is to elicit and document the requirement suchthat the ambiguities in the initial description of the system are clarified. The requirementshould be elicited from as many stakeholders as possible that might use the software.

Note that at this stage you should be focusing on the WHAT and not the HOW. Thedeliverable for this phase is the Requirements document. This document is the officialstatement of what your team must build. It should clearly specify the main components

and behavior of the software and its operating environment. Number individualrequirements so that you will able to refer to them in later phases of the project. (25%)

3. The next step will be the design of the software. You must use an Object-Orienteddesign strategy. The deliverable for this phase is the Design document that documents thedesign of the entire software. This document is basically a proposal for a solution thatsatisfies the requirements. (25%)

4. The forth step will be the implementation and testing of the software. Thedeliverable for this phase is the testing document and the source code files. (25%)

5. The final step will be the final delivery. The deliverable for this phase is the FinalProduct itself. The software must contain a ReadMe file, a User Manual, InstallationInstructions, and all the necessary source code files. (10%)

NOTE: All team members must take part in all project activities. While the volume of work of each group member on each project component may not be equal, their contribution to the overall project should equal out.


6/7

Project Website

The team must develop and maintain a project website for the instructor and all teammembers to visit. The instructor can view the website at any time during the semester, sokeep it up-to-date. The project website must contain at least the following items:

Project Information:Profile of team members (role/responsibility, etc.)Project overview

Current project statusArchive of Meeting Minutes for ALL meetingsElectronic copy of each project deliverable

Individual Information:Weekly status report a paragraph describing YOUR work effort for the week as itrelates to the projectWork log sheet a project timecard that shows date, start-time, end-time, work item, anddescription

The project Website will account for the remaining 10% of your project grade.

NOTE: I will be viewing the project website regularly to make sure that every teammember is attending the meetings and contributing to the project. Team members who arenot attending the meetings and contributing to the project will be considered as notcontributed to the deliverable in question and will be assigned zero credit for thisdeliverable.

Evaluation

Each deliverable will be graded and assigned an overall group mark. Each member willalso receive an individual scale. The individual scale is the average scale of your


7/7

performance in this deliverable rated by other members in the group and the instructor (0-100). The mark of each member for each deliverable is the group mark scaled by theindividual scale.

b tech cse project sommerville

Documents