Competence Assurance

Management System

12/20/20 1
 PURPOSE OF THE SYSTEM
•This system helps SNNPR CITA clients :
 to apply for competency online
 to apply for license online
•SNNPR CITA agents will get all records easily.
•the system will overcome the effort required for the user registration and report
generation.
SCOPE OF THE SYSTEM
•The scope of this project is to overcome the problem that exists in a current manual
competency issuance and data recording system of SNNPR CITA at regional level.
•The system is mainly for SNNPR CITA and its clients.

12/20/20 2
 OBJECTIVES OF THE PROJECT

 GENERAL OBJECTIVE
• To change the existing manual system of competency and licency assurance
system of the SNNP CITA to the web based system.
 SPECIFFIC OBJECTIVE
• Some specific objective of the proposed system are:-
 To make the request form web based and customer oriented.
 To generate the report of the user information for the agency.
 To help clients to apply online
 To Provide appointment for applied requests
 To fill the certificate form authomatically

12/20/20 3
SUCCESS CRITERIA OF THE PROJECT

12/20/20 4
 STATEMENT OF PROBLEM

• CITA collect the information in the region manually.

 The existing system has the following limitations:
 Inefficient organization of user’s information and records
 Information look up is cumbersome and time consuming
 Impedes the flow of critical information
 It is not cost effective
 Needs more man power
 Consumes large volume of paper work.
 Duplicated effort

12/20/20 5
 DEVELOPED SYSTEM

12/20/20 6
FUNCTIONAL REQUIREMENTS
 The functional requirement that the proposed system have to fulfill are listed as
follow:-
• This system should allow clients to apply online :
 For competency
 For license

• This system should allow applicants to be notified about their

application status
• This system should allow CITA agents to decide on application
requests on:-
Accept
Reject

12/20/20 7
Cont..
• This system should allows data manipulation
Insertion
Delete
Alter
Retrieve
• This system should allow CITA Agents to give assurance and register
clients
• This system should will generate the report

12/20/20 8
System Flowcharts

12/20/20 9
 SYSTEM MODELS

 SCENARIOS
• Scenario-based modeling represents the system from the user’s point of view.
• A scenario is a sequence of steps describing an interaction between a user
and a system.
• It enables you to understand how the user interacts with the software, uncovering
the major functions and features that stakeholder require of the system.

12/20/20 10
cont...
 USE CASE MODEL
• Use case identifies processes or activities that can be done within
the system.
• A use case is also a set of scenarios tied together by a common
user goal.
• A system use case model is composed of a use case diagram
and the accompanying documentation, the use cases , actors
and associations.
• It also describes a sequence of actions that provide a measurable
value to an actor.

12/20/20 11
use case diagram of central administrator

12/20/20 12
Use case diagram of zone user

12/20/20 13
Customer/client use case diagram

12/20/20 14
Cont.…
 Sequence Diagram
• Sequence diagrams are used to model the logic of usage scenarios or
the description of the potential way the system used.
• Sequence diagrams are a great way to validate and flesh out the logic
of use case scenarios and to document the design of the system.

12/20/20 15
System users login page sequence diagram

12/20/20 16
Zone system user registration sequence diagram

12/20/20 17
System user approve step sequence diagram for specific
customer

12/20/20 18
 NONFUNCTIONAL REQUIREMENTS

User interface and human factors

• In order to make our system more comfortable for the user and the customer we
use the user interface.
•It makes the system easy to use for both the user and customers.
• The basic information is restricted and interacted with the user and the customers
to decrease errors.

12/20/20 19
Main Home Page

12/20/20 20
Login Page

12/20/20 21
Central admin Home Page

12/20/20 22
 Zone user registration form page

12/20/20 23
 Customer request information viewing page

12/20/20 24
 Appointment page for the admin

12/20/20 25
Approval page for the client

12/20/20 26
Printable page of certificate

12/20/20 27
cont...

12/20/20 28
cont...
 Error handling and extreme conditions
• To control errors the system will generate different messages that let users
know what their error is.
• Data errors which are entered in to the system may not be completely avoided
but they can be minimized.
 System modifications
• When the users need another additional functionality or a change in the system,
there will be always changes when the system administrator identifies the
system need to be modified.

12/20/20 29
ER Diagram

12/20/20 30
RECOMENDATION
The printable page

File reading style

Using the existing frame work for more system awesome

12/20/20 31
 References

[Link] Sommerville (2009)Software Engineering Ninth Edition

[Link] [Link], Bruce [Link] ()Software engineering A
Practitioner’s Approach Eigth Edition
[Link] van Vliet(2007) Software Engineering: Principles and Practices
[Link] [Link], Michael [Link] Software Engineering Modern
Approaches Second Edition
5.E.M. Bennatan On Time, Within Budget Software Project
Management Practices and Techniques Second Edition

12/20/20 32