Software Engineering Documentation

Only available on StudyMode
  • Download(s) : 100
  • Published : September 8, 2011
Open Document
Text Preview
University of the East
Caloocan Campus
College Of Engineering
Department Of Computer Studies & Systems
2nd Semester S.Y. 2010 – 2011
Software Project Title:
“Equipment Borrowing System”
Computerized Borrowing System
Maintenance of the system in case there is no record for the new student of new equipment has arrived. Generate report of borrowing records on a daily basis.
Using of Barcode Reader
Viewing of borrowing history (by student or by date)
Programming Language:
Microsoft Visual Basic 2010 Express
Eclavia, John Edlin T.
Mutuc, Mikkho M.
Decapia, Neil Aldrin
Tolentino, Paul John

University of the East
Caloocan Campus
College Of Engineering
Department Of Computer Studies & Systems
Equipment Borrowing System
Barcode Reader
We, the students from the College of Engineering of University of the East – Caloocan, would like to propose an EQUIPMENT BORROWING SYSTEM for the benefit of the University This system will be more effective in terms of time management ease of use and reliability the system will monitor or keep track of the equipments that had been borrowed by the students or authorized employees of the School. We hope through the use of this system it will be more fast and reliable to borrow equipments for academic purposes. Thus, we are hoping that you will consider our proposal. PROPOSED BY:

Eclavia, John Edlin T.
Decapia, Aldrin _______________________ Mutuc, Mikkho M. Prof. Dimaano Tolentino, Paul John SWENG Adviser

Chapter I
1.1 Scope and Limitations
Our system is a computerized system for borrowing equipments such as digital equipments etc. for a school or a university. The students will be able to borrow a equipment using a computerized system. The system will feature a barcode reader for fast verification for students and the equipments that will be borrowed and for recording purposes. It also features of viewing all borrowing history. The viewing of borrowing history can be sorted by date or by student. Lastly, the system can generate the borrowing report on daily basis which means daily summary will be printed of the borrowing records for the day.

Model to be used

1.3 Prototyping Model
Often, a customer defines a set of general objectives for software but does not identify detailed input, processing, or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the adaptability of an operating system, or the form that human/machine interaction should take. In these, and many other situations, a prototyping paradigm may offer the best approach. The prototyping paradigm (as shown above) begins with requirements gathering. Developer and customer meet and define the overall objectives for the software, identify whatever requirements are known, and outline areas where further definition is mandatory. A "quick design" then occurs. The quick design focuses on a representation of those aspects of the software that will be visible to the customer/user. The prototype is evaluated by the customer/user and used to refine requirements for the software to be developed. Iteration occurs as the prototype is tuned to satisfy the needs of the customer, while at the same time enabling the developer to better understand what needs to be done. Ideally, the prototype serves as a mechanism for identifying software requirements. If a working prototype is built, the developer attempts to use existing program fragments or applies tools that enable working programs to be generated quickly.

Chapter II


University of the East

tracking img