GRADUATION PROJECT REPORT GUIDLINE

1
GRADUATION PROJECT REPORT GUIDLINE

• WHAT SHOULD WE INCLUDE IN EACH OF THE FOLLOWING
  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

• GRADUATION PROJECT REPORT GUIDLINES
• PROJECT ABSTRACT (SUMMARY)
• This should not be more than one page It
  should contain condensed statements extracted
  from the main 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, what
  are the recommended solution and the
  justification of the recommended solution
  by emphasising on the key benefits and
  costs of the new System as well as any
  Operational and technical concerns.
•         
• HINT - It is best to leave the Project summary
  as the last task of the report
  writing.

3

GRADUATION PROJECT REPORT GUIDLINES 1.
INTRODUCTION Introduction is the place for a
broad, general view of your material. a)
State your Purpose and Terms of Reference,
and indicate how far you are able to
carry them out. b) Provide Background
information, in which your reader will
need, 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) and
abbriviations that you intend to use in a
special sense.
4

• GRADUATION PROJECT REPORT GUIDLINES
• 1. INTRODUCTION
• 1.1 PROJECT OBJECTIVES
• List of the Objectives of the New System.
  (these should be very brief points)
  for example-
• To provide faster and more efficient services
  to the customers
• To set-up an environment to facilitate the
  current and future e-commerce System
  requirements etc...

5

GRADUATION PROJECT REPORT GUIDLINES 1.
INTRODUCTION 1.2 PROJECT SCOPE AND
CONSTRAINTS Project Scope means the
range or extent of the Project. It
helps to establish the boundaries of the
Requested Systems since it requires a
precise statement of the problem.
Project Constraint is a condition, restriction or
requirements that 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

GRADUATION PROJECT REPORT GUIDLINES 1.3
DEVELOPMENT METHODOLOGY This section
should contain the tools and techniques that are
used for the Development and
implementation of the Proposed 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
GRADUATION PROJECT REPORT GUIDLINES

• 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

GRADUATION PROJECT REPORT GUIDLINES 1.
INTRODUCTION 1.3 DEVELOPMENT METHODOLOGY
(Justification) 1.3.4 DATA BASE
ARCHITECTURE
ie Distributed Database Architecture such as
Single Database 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

GRADUATION PROJECT REPORT GUIDLINES .
INTRODUCTION 1.3 DEVELOPMENT METHODOLOGY
(Justification)

• 1.3.5 HARDWARE and NETWORK PLATFORMS
• i.e IBM PC, APPLE, HP, SUN
  SOLARIES, Windows NT Novel
  Netware etc.
• H/W AND NERTWORK CONFIGURATIONS
• (Ie. RAM, ROM, MPEC etc, ..)

10

GRADUATION PROJECT REPORT GUIDLINES 1.
INTRODUCTION 1.4 KEY PROJECT BENEFITS
Emphasise on the key Project Benefits.
This could include both tangible and
intangible benefits that are expected
once the system becomes operational.
e.g - Significant savings of up to 20
on Fleet administration Staff
costs - Up to 60
Reduction on telephone and telex costs
- Improved Customer relationship which will
have a positive affect on
Customers loyalty. etc.)
11

GRADUATION PROJECT REPORT GUIDLINES 1.
INTRODUCTION 1.5 PROJECT DEVELOPMENT PLAN
The Project Plan provides an overall
framework for managing the costs and
schedules of the Project. Project
planning takes place at the beginning and at the
end of each Project Phase.
GANTT Chart is a popular project planning and
scheduling tool. Use
MS-Project 2000 to draw your Project Plan.
12

GRADUATION PROJECT REPORT GUIDLINES 2.
CURRENT SYSTEM (EXISTING SYSTEM) A Brief
description about the Current Systems
Operational Environment and its major problems
and shorcomings will have to be considered under
this heading. Sufficient details have to be
given in order to enable the reader to
appriaciate and justfy the Development of
Proposed new System. Every organization (be
it a Commercial organization, School or Hospital)
has an Existing System or procedures. The
Existing System can be a Paper-based system
otherwise known Manual-based System or a Copmuter
Information System.
13

GRADUATION PROJECT REPORT GUIDLINES 2.
CURRENT SYSTEM (EXISTING SYSTEM) It is
necessary to study and analyze the Current System
to - Understand the shogrtcomings and
problems of the current system and
generate solutions to solve problems -
Replace the current system with an improved
version Information about the
Current System can be obtained from
several sources by applying the following Fact
Finding techniques individually or in
combinations- - User Interviews
- Questionnaires, - Observation,
- Document Review , - Sampling,
and Research.
14

GRADUATION PROJECT REPORT GUIDLINES 2.
CURRENT SYSTEM (EXISTING SYSTEM) When gathering
information about the Current System you should
focus your attention on the following 5 areas
- System Outputs,
- Inputs, -
Processes, - Timings
- System Controls. It is also
necessary to gather statistical information about
the Volumes, Sizes and frequencies of the
currrent System.
15

GRADUATION PROJECT REPORT GUIDLINES 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

GRADUATION PROJECT REPORT GUIDLINES 3.
PROPOSED SYSTEM (NEW SYSTEM) 3.1 LOGICAL
MODEL OF PROPOSED SYSTEM This section
will contain details about the main functionality
of the Proposed System. In other
word it will contain details of Logical Model of
the System, in which it will show what the
System must do to satisfy businees
information need rather than how it will be
accomplished physically.
17

• GRADUATION PROJECT REPORT GUIDLINES
• 3. PROPOSED SYSTEM (NEW SYSTEM) 3.1 LOGICAL
  MODEL OF PROPOSED SYSTEM
• Depending on the Systems Development
  methodology different set of CASE tools
  and techniques will be used for Data, Process
  and Object Modelling-
• If SSADM is used , Data Flow Diagrams (DFD),
  Entity Relationship Diagram (E-R Diagram)
  Decision Table, Decision Tree, Structured
  English will be used to explain the logic of the
  Functional processes.
• If OODM used then Unified Modeling Language
  (UML) Diagrams will be used (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 demonstration purpose or as a
  first version of the System for improvement !!!

18

• GRADUATION PROJECT REPORT GUIDLINES
• 3. PROPOSED SYSTEM (NEW SYSTEM)
• 3.2 PHYSICAL SYSTEM MODEL OF PROPOSED SYSTEM
• This section should contain details about
  the Physical Model of the Information
  System. The Physical System model must be built
  on on 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 Design
  will have to be addressed.

19

GRADUATION PROJECT REPORT GUIDLINES 3.
PROPOSED SYSTEM (NEW SYSTEM) 3.2 PHYSICAL
SYSTEM MODEL OF PROPOSED SYSTEM The
Physical System Specification should include the
followings according to the Methodology
used. SSADM METHODStructure Chart, System Flow
chart, Pseudocode, Input Screen Designs, Report
Layouts etc. OODM METHOD Package
Diagrams, Design Class Diagrams and refined
version of the UML Diagrams that have been
developed for Functional System have to be
incorporate. (Preferred)
20

GRADUATION PROJECT REPORT GUIDLINES 4.
SYSTEM TESTING STRATEGY

• This section should contain an outline System
  Test Plan. The purpose of the Test plan is to
  demonistrate that the System is tested
  according to a plan for every known
  eventualities and that the test results are keept
  as proofs.
• Regardless of how the System was developed,
  the System testing has 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 as proof of the System
  Testing.

21

GRADUATION PROJECT REPORT GUIDLINES 4.
SYSTEM IMPLEMENTATION STRATEGY

• Since most of the new System replaces an
  Existing system either a completely Manual system
  or an earlier automated system.
• Normally the Existing System is important and
  needs to be convertred to the format required in
  the new System. Thus an an outline Plan is
  required deal with existing DATA CONVERSION into
  new format and loaded on new Database structure.
• the most suitable type of SYSTEM CHANGEOVER
  method must also be specified for System
  Implementation.

22

GRADUATION PROJECT REPORT GUIDLINES 4.
SYSTEM IMPLEMENTATION STRATEGY

• DATA CONVERSION Is the activity to convert the
  old data into new System format. Data
  Conversion is often becomes a small project on
  its own and usually carried out in cooperation
  with the users.
• Sometimes Old Databases, used by the Existing
  Systems, are commonly reused in the New Systems,
  some requirements necessitate changes and
  reloading of Database contents.

23

GRADUATION PROJECT REPORT GUIDLINES 4.
SYSTEM IMPLEMENTATION STRATEGY

• SYSTEM CHANGEOVER Is the process of putting
  the new System in action and retiring the old
  System. THERE ARE FOUR SYSTEMS CHANGEOVER
  METHODS-
• a) DIRECT CUTOVER With Direct Cutover,
  the Old System stops and the New System
  starts simultaneously. This is the
  east expensive and most risky method.
• b) PARALLEL OPERATION With this
  method, both the Old and new Systems are
  operated for some period of time. This is
  the most expensive and least risky and safest
  method

24

GRADUATION PROJECT REPORT GUIDLINES 4.
SYSTEM IMPLEMENTATION STRATEGY

• SYSTEM CHANGEOVER c) PILOT OPERTATION
  A limited part of the organization uses the New
  System for a period of time while the old
  system continues to operate for the
  remaining part of organization. After the
  System proves successful at the pilot site it is
  implemented throughout the organization.
• d) PHASED CHANGEOVER One module of the
  new System at a time is implemented
  throughtout the organization until the system is
  entirely operational. Pilot and Parallel
  changeover methods represent compromise between
  Direct cutover and Parallel operation and are
  less risky than Direct Cutover and less costly
  than Parallel operation.

25

• GRADUATION PROJECT REPORT GUIDLINES
• MAINTEMANCE AND SUPPORT
• This section will only be present if you
  have any special Maintenance and Support
  arangements with the organization Or if there
  are any important Maintenance issues that you
  have to draw to the attention of the reader of
  the report.

26

• GRADUATION PROJECT REPORT GUIDLINES
• 6 OUTSTANDING ISSUES
• This section should contain brief
  information about the completion status of
  the Project.
• Information may be brief explanation about
  any unfinished project tasks due to time
  limitation or any other hindering factors.
  Any area of the System that requires further
  investigation, further work will have to be
  mentioned in this section .
• Also any concerns and/or Suggestions about
  the Project, as identified by the Original
  Project development team, may be stated in
  this section as a reference.

27

• GRADUATION PROJECT REPORT GUIDLINES.
• 7. APPENDICES
• The Report should include an Appendix if you
  need to attach supporting information to serve as
  sources of future reference.
• Eg. You might include Interview Questions and
  Answers. Hardcopy of any Screens, Reports,
  any System documentation that you
  collected and analyzed. Also any work in
  technical nature such as Data Normalization,
  Database Design, Program Listing, System
  Test results etc. should be included in this
  section as a proof. The Appendices section
  should also be organazed for clarity and
  readability.

28

• GRADUATION PROJECT REPORT GUIDLINES.
• 8. GLOSSORY
• Short definition of any technical terms i.e
  Jargons and abbreviations used in your report.
  (It should be in alphabetical order) eg.
  Abbreviation for Eastern Mediterranean
  University is (EMU)