Hi all ...
I'm new to the forum and actually lost !! ... I don't know if I'm posting at the right place, so be easy on me..
I'm a computer science student, and I want to develop a software as a graduation project for my BSc ... I'm thinking of an "Attendance Monitoring System" that uses finger prints to monitor employees attendance to a basic organization.
I'm currently at the requirement analysis phase ... I would go to an organization and collect my information, but those things aren't easy around here in JORDAN !! not much of help to be offered :(
Can you help me develop a policy to base my program on ... any view, post, reply and help is extremely appreciated.
MONabas wrote I'm a computer science student, and I want to develop a software as a graduation project for my BSc ... I'm thinking of an "Attendance Monitoring System" that uses finger prints to monitor employees attendance to a basic organization. I'm currently at the requirement analysis phase ... Can you help me develop a policy to base my program on ... any view, post, reply and help is extremely appreciated.
I'm currently at the requirement analysis phase ...
One technique which works very well for me is to just open a blank document and start typing anything that comes to mind about the topic at hand. I mean anything!
Then slowsly you'll begin to see common themes which will help you begin the outline/organization of your information.
For the requirements phase of your project, you might want to start by imagining that the product/software is already complete and that you're trying to sell it. So you're going to put the CD in a box and then come up with sales copy to put on the box:
Then proceed imagining that the customer openes the box and looks at the software's use manual. What would they see in there? How would they use the software? Who are the key users of the software? What are some of the system requirements?
Hope this helps!
Adrian
Oh !! thank you Adrian :D this really helps ... I will consider your suggestion and start work upon it .. thnx again :)
Monabas
Attendance registration using "finger print" to identify the person is no different to a generic attendance registrations system, where the "input" is either IDCards, Clock In, Timesheets etc. For the initial requirements, I'd suggest that you specify the requirements that are "technology independent". You'd probably have some keys areas: 1) register the subject: Normal subject data with expirations (valid access form 1-Jan-2010 till 30 Mar-2010 2) assign identification to subject: ID cards, finger printing, retina scans, voice print and some other BIO data (How you capture these things comes later in the DESIGN phase) 3) Location and Time: places and periods the subject has access too. Eg. Normal 9am-5pm. Out of hours 9-12, Crazy hours 12-9. Locations: Carpark, Lifts, and designated floor for out-of-hours and Crazy hours only. 4) Audit and Reporting: Normal access and breaches 5) clocking on and off (satisfying the above criteria) Draw a high-level entity realtionship model (or data Model using Classes), then state the declarative requirements (first). Usecases are behavioural things which are governed by the declarative requirements. Good luck
Attendance registration using "finger print" to identify the person is no different to a generic attendance registrations system, where the "input" is either IDCards, Clock In, Timesheets etc.
For the initial requirements, I'd suggest that you specify the requirements that are "technology independent". You'd probably have some keys areas:
1) register the subject: Normal subject data with expirations (valid access form 1-Jan-2010 till 30 Mar-2010
2) assign identification to subject: ID cards, finger printing, retina scans, voice print and some other BIO data (How you capture these things comes later in the DESIGN phase)
3) Location and Time: places and periods the subject has access too. Eg. Normal 9am-5pm. Out of hours 9-12, Crazy hours 12-9. Locations: Carpark, Lifts, and designated floor for out-of-hours and Crazy hours only.
4) Audit and Reporting: Normal access and breaches
5) clocking on and off (satisfying the above criteria)
Draw a high-level entity realtionship model (or data Model using Classes), then state the declarative requirements (first). Usecases are behavioural things which are governed by the declarative requirements.
Good luck
brought to you by enabling practitioners & organizations to achieve their goals using: