Sale!
Placeholder

Stock Ordering Database

10,000 3,000

Topic Description

Summary

Project Summary
The aim of this project was to develop a web based driven database for a small specialist sports
company so that information regarding stock and orders could be stored and searched for by
company sales representatives who require remote access to the system. The two main areas of
focus were system functionality and usability.
The project minimum requirements were:
? Investigate the appropriate concepts in order to allow an understanding of the user needs
for the database.
? Look at possible software tools in order to produce the database and the web based front
end for it.
? Examine and evaluate the impact of HCI issues related to the problem so to allow for
system usability.
? Develop the database which will satisfy the problem, with the main issues of placing
orders and stock control being forefront to the problem.
? Create and apply appropriate procedures to evaluate the solution.
My own personal objectives for this project were:
? Gain experience of using web development tools and improve my own understanding of
the programming languages involved.
? Further my knowledge of software development through applying a software
development methodology in a practical situation.
Achievements
I have successfully implemented a prototype system that meets the minimum requirements of the
project as well as allowing me to achieve my own personal objectives. The system also has other
non minimal functionality which I was able to implement within the time constraints of the
project schedule.

Table of Contents
1 Introduction 5
1.1 Background to the Problem 5
1.2 Scope of the Project 6
2 Background Research 7
2.1 Systems Development Methodologies 7
2.1.1 Structured Systems Analysis and Design 7
2.1.2 Evolutionary Prototyping 8
2.1.3 Systems Development Life Cycle Model 9
2.1.4 Waterfall Life Cycle Model 10
2.2 Database Management Systems 11
2.2.1 Oracle 11
2.2.2 SQL Server 2000 11
2.2.3 Ingres 11
2.2.4 DB2 12
2.2.5 Access 12
2.3 Web Development Tools 12
2.3.1 Dreamweaver 13
2.3.2 Front Page 2000 13
2.4 Web Page Scripting Language 13
2.5 Human Computer Interaction Issues 14
3 Analysis 15
3.1 Current Systems Procedures 15
3.1.1 Article Details 15
3.1.2 Order Details 15
3.1.3 Customer Details 16
3.2 Need For a New System 16
3.2.1 Data Duplication 16
3.2.2 Data Search Difficulties 17
3.2.3 Update and Delete Problems 17
3.3 User Requirements 17
3.4 Database Requirements 19
4 Database Design 20
4.1 Data Modelling 20
4.1.1 Entity-Relationship Model 20
4.1.2 Entity Types 20
4.1.3 Entity Relationships 21
4.1.4 Attributes 22
4.2 Logical Database Design 23
4.2.1 Mapping the E-R Model into Relational Tables 23
4.2.1.1 Mapping Entity Types 23
4.2.1.2 Mapping 1:1 Relationship Types 23
4.2.1.3 Mapping 1:N Relationship Types 23
4.2.1.4 Mapping M:N Relationship Types 23
4.2.1.5 Mapping Entity Sub-Types 24
4.2.1.6 Mapping Participation of Relationship 24
4.2.2 Relation Schema 24
4.3 Referential Integrity Rules 24
Table of Contents
4
4.3.1 Entity Integrity 25
4.3.2 Referential Integrity 25
4.4 Database Normalisation 25
4.4.1 Functional Dependencies 25
4.4.2 First Normal Form 26
4.4.3 Second Normal Form 26
4.4.4 Third Normal Form 27
4.4.5 Boyce-Codd Normal Form 28
5 Human Computer Interaction and Systems Interface Design 28
5.1 Human Computer Interaction Guidelines 28
5.2 Readability of Web Pages 28
5.3 Guessibility 29
5.4 Interface Design 29
6 Implementation 31
6.1 Database Implementation 31
6.1.1 Database Relationships 31
6.2 Interface Implementation 32
6.2.1 Web Page Layout 32
6.2.2 User Interface Architecture 32
6.3 SQL and the Database Connection 33
7 Testing and Evaluation 35
7.1 White and Black Box Testing 35
7.2 User Acceptance Testing 35
7.3 Evaluation 36
8 Conclusion 37
8.1 Future Enhancements
Appendix A – Personal Reflection 41
Appendix B – Database Design and Implementation 42
Appendix C – Website Architecture 53
Appendix D – Systems Testing 57
Appendix E – Evaluation 66
Appendix F – User Manual

PROJECT SAMPLE/DEPARTMENTS

REVIEW OUR SERVICES

SEE FAQ