Sie sind auf Seite 1von 5

TABLE OF CONTENTS

CHAPTER NO TITLE PAGE NO

1. INTRODUCTION 1
1. 1 DOMAIN STUDY 3
1. 2 PROBLEM STATEMENT 4

2. SYSTEM REQUIREMENT 6
2.1 PROPOSED SYSTEM 7
2.2 TOOLS SURVEY 9
2.3 OBJECT ORIENTED SOFTWARE DEVELOPMENT 44
LIFE CYCLE

3. DESIGN SPECIFICATION 47
3.1 UML DIAGRAM DESCRIPTION FOR PART A (LMS) 48
3.1.1 USECASE DIAGRAM 49
3.1.2 CLASS DIAGRAM 52
3.1.3 OBJECT DIAGRAM 53
3.1.4 ACTIVITY DIAGRAM 54
3.1.5 INTERACTION DIAGRAM 56
3.1.5.1 SEQUENCE DIAGRAM 56
3.1.5.2 COLLABORATION DIAGRAM 58
3.1.6 STATE CHART DIAGRAM 59
3.1.7 COMPONENT DIAGRAM 60
3.1.8 DEPLOYMENT DIAGRAM 61
3.2 UML DIAGRAM SPECIFICATION FOR PART B () 62
3.2.1 USECASE DIAGRAM 63
3.2.2 CLASS DIAGRAM 66
3.2.3 OBJECT DIAGRAM 67
3.2.4 ACTIVITY DIAGRAM 68
3.2.5 INTERACTION DIAGRAM 70
3.2.5.1 SEQUENCE DIAGRAM 70
3.2.5.2 COLLABORATION DIAGRAM 72
3.2.6 STATE CHART DIAGRAM 73
3.2.7 COMPONENT DIAGRAM 74
3.2.8 DEPLOYMENT CHART DIAGRAM 75

4. DATA BASE DESIGN 76

5. OUTCOME ANALYSIS 82
6. CONCLUSION 92

7. REFERENCES 95
LIST OF FIGURES

FIGURE FIGURE NAME PAGE


NO NO

2.1 Class 11
2.2 Interface 12
2.3 Collaboration 12
2.4 Use case 13
2.5 Active class 13
2.6 Component 14
2.7 Node 14
2.8 Interaction 15
2.9 State Machine 15
2.10 Package 16
2.11 Note 16
2.12 Dependency 17
2.13 Association 17
2.14 Generalization 18
2.15 Realization 18
2.16 Use case notation for an Actor 20
2.17 Use case notation for use case 21
2.18 Use case notation for Association 21
2.19 Use case example 21
2.20 Communicates relationship 22
2.21 An example of an extend relationship 22
2.22 An example of include relationship 23
2.23 An example of generalization relationship 23
2.24 An example of use case diagram for hospital management 24
2.25 Class diagram representation 25
2.26 Class diagram multiplicity 27
2.27 An example of class diagram for stock management 27
2.28 Object diagram of an order management system 29
2.29 Representation of object 30
2.30 Representation of an actor 30
2.31 Representation of lifeline 31
2.32 Representation of an activation 31
2.33 Representation of message 31
2.34 An example of sequence diagram for hotel reservation 32
2.35 An example of collaboration diagram for an order management system 33
2.36 An example of state chart diagram for online banking system 34
2.37 Notation of activity state 36
2.38 Notation of transition 36
2.39 Notation of swamlane 36
2.40 Notation of initial state 37
2.41 Notation of final state 37
2.42 Notation of synchronization bar 37
2.43 Flow of an activity diagram 39
2.44 An example of an activity diagram for an order management system 40
2.45 Component of component diagram 41
2.46 Dependency of component diagram 41
2.47 An example of component diagram for railway reservation system 42
2.48 Relationships among software and hardware components 43
2.49 Software Development Life Cycle 46

PART A : LIBRARY MANAGEMENT SYSTEM


3.1 Use Case diagram for Library Management System 49
3.2 Use Case diagram for library management System 50
3.3 Class diagram for Library Management System 52
3.4 Object diagram for Library Management System 53
3.5 Activity diagram for Library Management System 54
3.6 Activity diagram for Library Management System 55
3.7 Sequence diagram for Library Management System 56
3.8 Sequence diagram for Library Management System 57
3.9 Collaboration diagram for Library Management System 58
3.10 State Chart diagram for Library Management System 59
3.11 Component diagram for Library Management System 60
3.12 Deployment diagram for Library Management System 61

PART B : ATM SYSTEM


3.13 Use Case diagram for ATM System 63
3.14 Use Case diagram for ATM System 65
3.15 Class diagram for ATM System 66
3.16 Object diagram for ATM System 67
3.17 Activity diagram for ATM System 68
3.18 Activity diagram for ATM System 69
3.19 Sequence diagram for ATM System 70
3.20 Collaboration diagram for ATM System 72
3.21 State Chart diagram for ATM System 73
3.22 Component diagram for ATM System 74
3.23 Deployment diagram for ATM System 75
LIST OF TABLES

PART A : LIBRARY MANAGEMENT SYSTEM


Table Table Name Page
No No
4.1 Database design for Book 77
4.2 Database design for Librarian 77
4.3 Database design for Transaction 78
4.4 Database design for Member Record 78
4.5 Database design for Bill 79
5.1 Outcome analysis for Book 83
5.2 Outcome analysis for Librarian 84
5.3 Outcome analysis for Transaction 85
5.4 Outcome analysis for Member 86
Record
5.5 Outcome analysis for Bill 87

PART B : ATM SYSTEM

Table Table Name Page


No No
4.6 Database design for Customer 80
4.7 Database design for Vendor 80
4.8 Database design for Bank 80
4.9 Database design for Credit Card 81
4.10 Database design for Receipt 81
4.11 Database design for Item 81
5.6 Outcome analysis for Customer 88
5.7 Outcome analysis for Vendor 89
5.8 Outcome analysis for Bank 89
5.9 Outcome analysis for Credit card 90
5.10 Outcome analysis for Receipt 90
5.11 Outcome analysis for Item 91

Das könnte Ihnen auch gefallen