Google Apps for Education

TABLE OF CONTENTS

Declaration

Approval H

Dedication

Acknowledgement iv

List of Figures V

List of Tables vi

List of Appendices vii

CHAPTER ONE 1

1.1 Introduction 1

1.2 Background Information 1

1.3 Statement of the problem 1

1.4 Objectives 1

1.4.1 Main objective 1

1.4.2 Specific objective 2

1.5 Scope of the project 2

1.5.1 System Scope 2

1.5.2 Geographical Scope 2

1.6 Significance of the project 3

CHAPTER 2 5

LITERATURE REVIEW 5

2.0 Introduction 5

2.1 Information System 5

2.1.1 Types of Information System 6

Transaction Processing Systems 6

Management Information Systems 6

Decision Support Systems 6

2.2 Management Information System 7

2.3 Historical Perspectives 7

2.3.1 The “effect” paradigm 8

viii

2.3.2 The “conditions” paradigm .8

2,3.3 The “interactions” paradigm 9

2.3.4 The “computer supported” paradigm 9

2.4 Relationship to Other Concepts 10

2.5 Development of Collaboration Skills 10

2.6 Challenges in Collaboration 11

2.7 Future Prospects 11

CHAPTERTHREE 13

METHODOLOGY 13

3.1 Introduction 13

3.1.1 Waterfall Model 13

3.1.2 Weakness of waterfall model 13

3.1.3 Agile Methodology 13

3.1.4 Comparison between Agile and Waterfall 14

3.1.5 Reasons for using Agile Methodology 14

3.2 Google Apps Deployment Methodology 15

3.3 Mobile Application Development MethodologyV3 15

3.4.1 Observation 16

3.4.2 Brain-Storming Sessions 16

3.4.3 Captured System Requirements 16

3.5 System Design Techniques 16

3.5.1 Storyboarding 17

3.5.2 UML techniques 17

3.6 Design 17

3.6.1 User Interface Overview 17

UI Element Description 17

3.7 Application Building 18

3.7.1 Programming Technique Used 18

3.8 Application Testing Techniques 18

ix

3.8.1 White box Testing .18

3.8.2 Blackbox Testing 18

3.9 Conclusion 19

CHAPTER 4 20

SYSTEM REQUIREMENT ANALYSIS AND DESIGN 20

4.1 System Architecture 20

Figure 4.1 how cloud computing works 20

4.1.1 Understand the Architecture 21

4.1.2 App container model 21

4.1.3 Programming model 21

4.1.4 App lifecycle at a glance 22

4.1.5 Security model 22

4.2 System Requirements 22

4.2.1 Functional Requirements 22

4.2.2 Non-Functional Requirements 23

4.2.3 Hardware Requirements 23

4.2.4 Software Requirements 24

Platform 24

Languages 24

Browsers 24

Desktop 25

Mobile and tablet 25

4.3 Google Apps Use Case diagram 26

4.3.1 Explanation of the above use cases 28

4.4 Sequence Diagram of how to log into campus email system 28

4.6 User Interface Design 29

4.7Summary 29

CHAPTER 5 30

THE CAMPUS EMAIL SYSTEM 30

x

5.1 Screen shots for Campus Email system user interface 30

5.1.1 Screen shots of our project interface 30

Login panel for students 31

User authentication 31

Drive 32

Customized sites to School domain 33

Calendars 33

One day view calendar 33

A Weeks view calendar 34

A month view of calendar 34

5.2 Screen shots Email system admin panel 35

Domain users display page 35

Setup page 35

Security settings page 36

Reports page 36

5.3 Use Case Test Results 37

5.4 Requirement Test Results 37

CHAPTER 6 39

CONCLUSION AND RECOMMENDATIONS 39

6.0 Introduction 39

6.1 Achievements 39

6.2 Limitations 39

6.3 Challenges 40

6.2 Conclusions 40

6.3 Recommendations 40

REFERENCES 42

APPENDICES 46