graduation project report guidilens

8/22/2019 Graduation Project Report Guidilens

1/28

GRADUATION PROJECT

REPORT GUIDLINEWHAT SHOULD WE INCLUDE IN EACH OF THEFOLLOWING REPORT SUB HEADINGS ?

WHERE AND HOW TO OBTAIN THE INFORMATION ?

ABSTRACT (summary)INTRODUCTION CURRENT SYSTEM (EXISTING SYSTEM)

PROPOSED NEW SYSTEM APPENDICES USER GUIDE GLOSSORY


2/28

GRADUATION PROJECT REPORT GUIDLINES

PROJECT ABSTRACT (SUMMARY)

This should not be more than one page

It should contain condensed statements extracted from themain body of the report to convey the main theme of the project

to the readers.

ie. very brief descriptions of the project, how the project initiated, whatare the recommended solution and the justification of therecommended solution by emphasising on the key benefits andcosts of the new System as well as any Operational and technicalconcerns.

HINT :- It is best to leave the Project summary as the last task of thereport writing.


3/28


1. INTRODUCTION

Introduction is the place for a broad, general view ofyour material.

a) State your Purpose and Terms of Reference, and indicatehow far you are able to carry them out.

b) Provide Background information, in which your reader willneed, and which he may not know or clearly remember.

c) Announce the arrangement of your Main sections.

d) Define and clarify the technical terms (Jargons) andabbriviations that you intend to use in a special sense.


4/28


1. INTRODUCTION1.1 PROJECT OBJECTIVES

List of the Objectives of the New System. (these should bevery brief points) for example:-

To provide faster and more efficient services to the customers

To set-up an environment to facilitate the current andfuture e-commerce System requirements etc...


5/28


1. INTRODUCTION

1.2 PROJECT SCOPE AND CONSTRAINTS

Project Scope means the range or extent of the Project. Ithelps to establish the boundaries of the Requested Systemssince it requires a precise statement of the problem.

Project Constraint is a condition, restriction or requirementsthat the System must satisfy.

A constraint can be in terms of Time, Money or Technical

concern.

e.g:- Project must be ready on 1st January 2004- The project cost must not exceed $100,000- The new system must be based on companies existing

Hardware platform etc..


6/28


1.3 DEVELOPMENT METHODOLOGY

This section should contain the tools and techniques that areused for the Development and implementation of theProposed System.

You should also give a brief justification of the the Method

and technique that you chose for this project.

1.3.1 Systems Development Methods and techniques such as:-

* Structured Systems Analysis and Design Methodology

* Rapid Application Development technique (RAD)

* Object-Oriented Delopment Methodology (OODM) ***Preferred Methodology for Graduation Project is OODM.


7/28


1.3.2 Programming Languages

- Structured Programming Languages

- Object-oriented Programming Languages (OOP)***

(Preferred Language is OOP)

1.3.3 System Architecture and Processing Methods,

(i.e, Client/Server architecture. 2 tiers, 3 tiere,

Web-centric, On-line, Batch processing etc...


8/28


1. INTRODUCTION

1.3 DEVELOPMENT METHODOLOGY (Justification)

1.3.4 DATA BASE ARCHITECTURE

ie; Distributed Database Architecture such as SingleDatabase Server, Replicated Database Server,Partitioned Database server etc..)

DATA BASE MANAGEMENT SYSTEMS (DBMS)

- Relational Data Base Management Systems (RDBMS)- Object Oriented Database Management Systems (ODBMS)

- (i.e Oracle, SQL-Server, MS- Access etc )


9/28

1.3.5 HARDWARE and NETWORK PLATFORMS

i.e: IBM PC, APPLE, HP, SUN SOLARIES, Windows NTNovel Netware etc.

H/W AND NERTWORK CONFIGURATIONS

(Ie. RAM, ROM, MPEC etc, ..)


. INTRODUCTION

1.3 DEVELOPMENT METHODOLOGY (Justification)


10/28


1. INTRODUCTION

1.4 KEY PROJECT BENEFITS

Emphasise on the key Project Benefits.

This could include both tangible and intangible benefits thatare expected once the system becomes operational.

e.g - Significant savings of up to 20% on Fleet administrationStaff costs

- Up to 60% Reduction on telephone and telex costs

- Improved Customer relationship which will have apositive affect on Customers loyalty. etc.)


11/28


1. INTRODUCTION

1.5 PROJECT DEVELOPMENT PLAN

The Project Plan provides an overall framework formanaging the costs and schedules of the Project.

Project planning takes place at the beginning and at theend of each Project Phase.

GANTT Chart is a popular project planning and schedulingtool.

Use MS-Project 2000 to draw your Project Plan.


12/28


2. CURRENT SYSTEM (EXISTING SYSTEM)

A Brief description about the Current Systems OperationalEnvironment and its major problems and shorcomings will haveto be considered under this heading.

Sufficient details have to be given in order to enable the readerto appriaciate and justfy the Development of Proposed newSystem.

Every organization (be it a Commercial organization, School orHospital) has an Existing System or procedures.

The Existing System can be a Paper-based system otherwiseknown Manual-based System or a Copmuter Information System.


13/28



It is necessary to study and analyze the Current System to:

- Understand the shogrtcomings and problems of the currentsystem and generate solutions to solve problems

- Replace the current system with an improved versionInformation about the Current System can be obtained fromseveral sources by applying the following Fact Finding

techniques individually or in combinations:-

- User Interviews- Questionnaires,- Observation,- Document Review ,- Sampling, and Research.


14/28



When gathering information about the Current System youshould focus your attention on the following 5 areas:

- System Outputs,- Inputs,- Processes,- Timings- System Controls.

It is also necessary to gather statistical information about theVolumes, Sizes and frequencies of the currrent System.


15/28


3. PROPOSED SYSTEM (NEW SYSTEM)

Propose a feasible SOLUTION system to solve the Existing

Systems problems as well as providing new functionality to

fulfill new user requirements.

3.1 LOGICAL MODEL OF PROPOSED SYSTEM

3.2 PHYSICAL SYSTEM MODEL


16/28




This section will contain details about the main functionality of theProposed System.

In other word it will contain details of Logical Model of the System, inwhich it will show what the System mu st do to s atis fy bus inees

information need rather than how it will be accomplished physically.


17/28




Depending on the Systems Development methodology different setof CASE tools and techniques will be used for Data, Process andObject Modelling:-

If SSADM is used , Data Flow Diagrams (DFD), Entity RelationshipDiagram (E-R Diagram) Decision Table, Decision Tree, StructuredEnglish will be used to explain the logic of the Functional processes.

If OODM used then Unified Modeling Language (UML) Diagrams will beused (Preferred)

. The required UML Diagrams are:-Use-case Diagrams with Use Case Specifications, Class Diagram,Sequence Diagram, and Statechart.

NOTE:- System Prototype may also be developed for demonstrationpurpose or as a first version of the System for improvement !!!


18/28



3.2 PHYSICAL SYSTEM MODEL OF PROPOSED SYSTEM

This section should contain details about the Physical Model of theInformation System. The Physical System model must be built onon the Systems Logical Model and address the actual methods of

Implementation.

Input Design, Output Design, User Interfaces ,System Interfaces and Navigation diagram,

System Security and Controls, Back-up recovery Procedures

Data Design (Normalisation) and Physical Database Designwill have to be addressed.


19/28



3.2 PHYSICAL SYSTEM MODEL OF PROPOSED SYSTEM

The Physical System Specification should include the followingsaccording to the Methodology used.

SSADM METHOD

Structure Chart, System Flow chart, Pseudocode, Input ScreenDesigns, Report Layouts etc.

OODM METHOD ***

Package Diagrams, Design Class Diagrams and refined version ofthe UML Diagrams that have been developed for Functional Systemhave to be incorporate. (Preferred)



20/28

This section should contain an outline System Test Plan.

The purpose of the Test plan is to demonistrate that theSystem is tested according to a plan for every knowneventualities and that the test results are keept as proofs.

Regardless of how the System was developed, the System testinghas the following objectives:-

- Perform a final test of all Programs- Demonistrate that Users can interact with the System Successfully- Verify that all System components are integrated properly and that

actual processing situation will be handled correctly.- Confirm that the information System can handle predicted volumes

of data in a timely and efficiently manner.

Hard Copy of The Test results must be included in the Appendicies asproof of the System Testing.


4. SYSTEM TESTING STRATEGY



21/28

Since most of the new System replaces an Existingsystem either a completely Manual system or anearlier automated system.

Normally the Existing System is important and needsto be convertred to the format required in the newSystem.

Thus an an outline Plan is required deal with existingDATA CONVERSION into new format and loaded onnew Database structure.

the most suitable type of SYSTEM CHANGEOVERmethod must also be specified for SystemImplementation.


4. SYSTEM IMPLEMENTATION STRATEGY



22/28

DATA CONVERSION

Is the activity to convert the old data into newSystem format.

Data Conversion is often becomes a small projecton its own and usually carried out in cooperationwith the users.

Sometimes Old Databases, used by the ExistingSystems, are commonly reused in the New

Systems, some requirements necessitate changesand reloading of Database contents.





23/28

SYSTEM CHANGEOVERIs the process of putting the new System in action and retiring theold System.

THERE ARE FOUR SYSTEMS CHANGEOVER METHODS:-

a) DIRECT CUTOVER

With Direct Cutover, the Old System stops and the NewSystem starts simultaneously.

This is the east expensive and most risky method.

b) PARALLEL OPERATION

With this method, both the Old and new Systems areoperated for some period of time.

This is the most expensive and least risky and safestmethod





24/28

SYSTEM CHANGEOVERc) PILOT OPERTATION

A limited part of the organization uses the New System for aperiod of time while the old system continues to operate for theremaining part of organization.

After the System proves successful at the pilot site it isimplemented throughout the organization.

d) PHASED CHANGEOVER

One module of the new System at a time is implemented

throughtout the organization until the system is entirelyoperational.

Pilot and Parallel changeover methods represent compromisebetween Direct cutover and Parallel operation and are less risky thanDirect Cutover and less costly than Parallel operation.





25/28


5. MAINTEMANCE AND SUPPORT

This section will only be present if you have any specialMaintenance and Support arangements with the organization

Or if there are any important Maintenance issues that youhave to draw to the attention of the reader of the report.



26/28


5.6 OUTSTANDING ISSUES

This section should contain brief information about thecompletion status of the Project.

Information may be brief explanation about any unfinishedproject tasks due to time limitation or any other hinderingfactors. Any area of the System that requires further

investigation, further work will have to be mentionedin this section .

Also any concerns and/or Suggestions about the Project, asidentified by the Original Project development team, may be

stated in this section as a reference.



27/28

GRADUATION PROJECT REPORT GUIDLINES.

7. APPENDICES

The Report should include an Appendix if you need to attachsupporting information to serve as sources of futurereference.

Eg. You might include Interview Questions and Answers.

Hardcopy of any Screens, Reports, any Systemdocumentation that you collected and analyzed.

Also any work in technical nature such as DataNormalization, Database Design, Program Listing,

System Test results etc. should be included in this sectionas a proof.

The Appendices section should also be organazed for clarityand readability.



28/28

GRADUATION PROJECT REPORT GUIDLINES.

8. GLOSSORY

Short definition of any technical terms i.e Jargonsand abbreviations used in your report. (It should bein alphabetical order)

eg. Abbreviation for Eastern MediterraneanUniversity is (EMU)

graduation project report guidilens

Documents