Scribd
Upload
104 views31 pages

Ambo University: Institute of Technology

This document describes the design of a Graduates Credentials Verification System for Ambo University. It includes class type architecture with different layers, class modeling diagrams, state chart diagrams for certificate verification, collaboration diagrams for login, component diagrams, deployment diagrams showing a client-server architecture, persistence modeling diagrams, user interface designs including home pages, and an overview of final testing, training and hardware/software requirements. The system will be developed using object-oriented design principles and implemented using technologies like PHP, MySQL and deployed on a server.

Uploaded by

Ahmedkan Proof
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
104 views31 pages

Ambo University: Institute of Technology

This document describes the design of a Graduates Credentials Verification System for Ambo University. It includes class type architecture with different layers, class modeling diagrams, state chart diagrams for certificate verification, collaboration diagrams for login, component diagrams, deployment diagrams showing a client-server architecture, persistence modeling diagrams, user interface designs including home pages, and an overview of final testing, training and hardware/software requirements. The system will be developed using object-oriented design principles and implemented using technologies like PHP, MySQL and deployed on a server.

Uploaded by

Ahmedkan Proof
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 31

Ambo University

Institute of Technology
Department of Computer Science

GCVSAU

Graduates Credentials Verification System for Ambo


University
1
System Design
. System Design Using Object-Oriented
Paradigm Improve the use case model
objects interactions and behaviors
. Transformation of analysis models of the
problem space into design models (based
on the solution space).

2
Outline

Class type architecture


Class modeling
State chart modeling
Collaboration Modeling
Component Modeling
Deployment modeling
Persistence modeling
User Interface design
3
Class type architecture

 Is how the system works and interacts with the user by


dividing work into different layers.
These layers are:
 interface layer
 control layer
 domain layer
 persistent layer and
 system layer

4
Class modeling

 Three contents of Class:


The name of the class.
The attributes of the class.
The operation of the class.
 It focuses on the solution domain
 It describes the structure of the system also
classes abstraction of set of object.

5
Class modeling Diagram
6
State chart modeling

Is the events that cause the transition from


one state to the other and actions that
result from a state change.
depicts the state of objects as their attributes
change from one state to the other state.

7
State Chart Diagram for Certificate Verification.
8
Collaboration Modeling

 is an illustration of the relationships and interactions


among software objects .
 are best suited to the representation of simple interactions
among relatively small numbers of objects.
 As the number of objects and messages grows, a
collaboration diagram can become difficult to read .It is used
to show some data flows between objects and the interaction
caused between them.

9
Collaboration Diagram for Login 10
Component Modeling

It shows how components are wired together


to form larger components or software systems.

11
Component Diagram

12
Deployment Diagram
shows physical view of system
takes software into real world
 shows how software gets assigned to
hardware and how communicates.

13
Client Machine

:Chrome TCP/IP
Web Server Admin

:E xp l o r e r
:XAMPP

:Mozilla

PHP

Central Data Base

:MYSQL

14
Architecture of the system is client server.

 Clients are responsible for:-


Receiving inputs from user
Checking range of performance
Server responsible for:-
Transaction performance
Guaranteeing the integrity of data.
Putting backup of database

15
Persistence Modeling
• It describes the persistent data aspect of
software system.

16
Persistence Modeling Diagram

17
User interfaces

User interface design is the specification of the interaction


between the system users and a system.
Navigation mechanism is part of user interface that takes
the user form one part of the system to the other user
system.
 Input design is about designing a form and its controls for
GUI system.
Output design is about designing reports like detailed,
summarized,and etc.

18
Home Page of the System

19
Home Page for Company Registration Form.

20
Home Page for Employee Registration Form.

21
Home Page for Admin of the System

22
Home Page for Registrar of the System.

23
Home Page for Verify Request

24
Chapter 5
Over view
 Final Testing System
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing
 Hardware software acquisitions

etc--

25
Introduction

 Implementation refers to the coding of the


all documents gathered starting from
requirement analysis to Design phase.
 All documents, business logic, information
gathered are designed into the code so that
the system will be implemented for the user
to be used for the purpose it developed

26
Final Testing

27
Cont..

28
Cont--

 Unit Testing The graduates Credential Verification System


modules are tested by unit testing
Black box
White box
 Integration Testing After unit testing, the each modules where integrated
together and is tested for its fitness with each other and with the systems
functionality
 System Testing Verification system: is functionally tested based
on the use case model developed during the analysis phase.
operationally tested based on requirements
It shows also intended to demonstrate whether the system meets it’s
objectively or no,t.
 Acceptance Testing
 Hardware and Software Configuration
• Production environments ---------Recommended - 32-bit OS with Intel/AMD 2.0
GHZ+ CPU
• RAM--------------------------------Recommend minimum 4 GB 29
Cont---
• Additional disk space for storage------ Temp files space- The store requires 5GB
• Operating system----------- Windows 2000, XP, Vista, and Windows 7, window 8
etc.
• Monitor--------------- Display minimum resolution 1024 x 768
 Training
 Installation Process
Since we are developing web based project which
can be hosted on the server, our system does not
need installing it on a particular machine. So system
cannot need installation process. It can be accessed
using the URL given to it and browsing the URL to
get the access to the system.

30
O U
K Y
AN
T H
31

You might also like