Chapter 4

CHAPTER 4: DESIGN PHASE
4.1 Introduction
This design phase will chiefly concentrate on the system design package diagram, program
design, sequence diagram, class diagram and interface design. This stage is primarily
concerned with the design of input and screen output interface for the system. It includes
the development of the objectives of the proposed system.
4.2 System Design

System design is the procedure or craft of characterizing the design, components, modules,
interfaces and information for the framework to fulfil determined prerequisites and the
utilization of the framework hypothesis to product improvement. Design alludes to
technical specifications that will be connected in executing the proposed system. The
design of the career guidance system concentrates on the essential components that ought
to meet and these incorporate such variables as user-friendly interfaces.
4.2.1 Input Design

Input design is the process of changing user-originated input to a computer-based format.
Information are gathered and sorted out into groups of comparative data. Fitting
information media are chosen for processing. The objective of designing input data is to
make entry as simple, and logical free form errors.
In the proposed system data must be exact and complete. The inputs incorporate the user
name and password to login. In any case, if the understudy is new there will be
requirement for supplying enrolment/registration data. These subtle elements are entered in
by the executive by means of the utilization of the content passage keys. The registration
data is of character sort empowering a change of most extreme number of characters to be
utilized considering the required data. The information is outlined utilizing Input controls,
for example, Textbox, and Label, If not error messages are shown to the user and she
cannot continue to the following phase of activity unless she remedies her information. The
information acceptance is a technique of the proposed system gives checks to the

consistency, sequence and completeness of the system.
4.2.2 Processing Design
Knowledge-based career guidance system flow chart
The flow chart endeavours to give an outline of the operations executed in the system. It
shows the procedures required in the human-interface collaboration of the proposed
system. The user starts by entering her user name and password, on the off chance that she
is as now a user of the system and has a current and working account with career guidance
system. The various Career Guidance administrations are then shown for her to choose that
what she wishes to do and afterwards she does her operations appropriately. In the event
that then again, the user is not registered, access would be denied until she has finished all
essential enlistment necessities.
Figure 1: flowchart for proposed system
Activity diagrams
Figure 2: activity diagram for student
Figure 3: activity diagram for administrator
4.2.3 Output Design

Computer output is the most imperative and direct basis of information to the user. Wellorganized, comprehensible output design should enhance the system, and associations with
the user. A noteworthy type of output is the printed copy from the printer. It contains the
results of the input process. The output design is projected in type of interface, which are
collaborating with the students. Output likewise gives a way of storage by copying the
outcomes for later reference.
4.2.4 How Will The System Work?

In the system each subject is given a numerical weight and each subject is then allocated to
A level combinations. When the student had entered subjects and grades, the system will
compute weights grouping by subject type. A level combinations are then allocated or
matched with degrees.
For the administrators and students to use the system they have to follow through the
following steps:
Logon to the user interface for the career guidance system

Open the career guidance system
Create account
On the user interface form, open the service required
Explore different career options on the web site.
4.3 Architectural Design

The primary part of the system form 3-tier architecture. The presentation tier consists of
end client machines such as portable PCs and tablets having web browsers such as Chrome
and Mozilla Firefox that show website page permitting access to the knowledge-based
career guidance system. The middle tier comprises of a web server such as Apache that
connects with the web browsers at end client machines furnishing them with web pages.
On the data tier dwells the database servers which contains the database managemnt
system.the database server, webserver, and the Administrators PCs are associated through
a fast Local Area Network.
Figure 4: architectural design for proposed system
4.4 Physical Design

This includes the development from the logical procedure and information modules to the
physical procedure and data modules. Blue rectangles assign machines, dark rectangles
assign programming/framework parts, red arrow lines assign physical correspondence
channels of machines, green arrow and lines assign logical correspondence between
components having a place with discrete machines, while dark arrows and lines assign
logical correspondence between components inside the same machine.
Figure 5: physical design
4.4.1 How Software and Hardware Interact

The software and the hardware devices interact simply as the applications installed on the
hardware present. This system is designed to suit the hardware components already in use.
It will be on the standalone computers and as a future development, the system will be on
the server to allow for online interaction to all the devices connected to that network.
4.5 Database Design

A database management system is a set of programs that empowers the creation and
upkeep of a gathering of related information. The DBMS and related projects access,
control, ensure, and deal with the data. The principal motivation between of a DBMS is to
give a solid, persistent data storage facility and the systems for productive, advantageous
information access and recovery. The database intended for the career guidance system is
planned with the idea of making a database for the users, profession data and activity.
Despite the sort of information structure utilized, the goals of the databases are:
Accuracy and trustworthiness
Successful recuperation from disappointment
Privacy and security information
Good general execution
Figure 6: context diagram for proposed system
Figure 7: L1 DFD for proposed system
4.5.1 Entity Relationship Diagram

The entity relationship diagram gives every one of the connections between the entities
inside the system. It likewise demonstrates which entity offers data to the next and which
entity gives information to the other and which entity has which information or attributes
belonging to other table. All career guidance exercises subtle elements will be done on the
main server and stored in the database. The users carry out their career guidance
applications through the standalone system and will be connected to the organisation
database on using the LAN.
Database tables
Courses (faculty id, id, codename)
Faculty (id, name code, description)
Combinations (id, code, class type)
A level subjects (id, subject code, id, subject name, subject type)
Job requirements (id, job id, programme code)
Jobs (id, name, description)
A level queries (id, session id, grade, subject code, user id)
Academic levels (id, code, name)
O level subjects (id, subject code, subject type, subject name)
Users (id, firstname, lastname, email, username, sex)
Combinationsdegrees (id, comb id, degree id)
Combinationjobs (id, comb id, job id)
4.6 Program Design

This stage takes a gander at how the system will be functioning and it displays the
procedures that are included in the system that is being designed.
Figure 8: sequence diagram
4.7 Interface Design

A user interface is a system that allows the association between a person and a computer.
Accordingly it characterises how clients connects with the career guidance system and how
the system captures data from the users. The main menu will contain a few menus to
browse. A graphical user interface is the best in light of the fact that the framework must be
easy to understand.
Figure 9: login form
Figure 10: registration form
Figure 11: main menu
Figure 12: change password form
4.8 Conclusion
The design phase characterised how the system would function in the actual environment
and the specifications of the components of the software that is going to be developed
defined in detail. The desired system is being composed and the equipment and software
and the hardware and software requirements have been chosen which will be utilised
together with the system. The system has been outlined in a way that the clients will think
that its simple to utilise, simple to keep up and does not bring about issues and that its
capacities or execution is solid.

Chapter 4

Uploaded by

Copyright:

Available Formats

Chapter 4

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 4

Uploaded by

Copyright:

Available Formats

CHAPTER 4: DESIGN PHASE

4.2 System Design

4.2.1 Input Design

information acceptance is a technique of the proposed system gives checks to the

Figure 1: flowchart for proposed system

Figure 2: activity diagram for student

Figure 3: activity diagram for administrator

4.2.3 Output Design

4.2.4 How Will The System Work?

Logon to the user interface for the career guidance system

4.3 Architectural Design

Figure 4: architectural design for proposed system

4.4 Physical Design

Figure 5: physical design

4.4.1 How Software and Hardware Interact

4.5 Database Design

Accuracy and trustworthiness

Successful recuperation from disappointment

Privacy and security information

Good general execution

Figure 6: context diagram for proposed system

Figure 7: L1 DFD for proposed system

4.5.1 Entity Relationship Diagram

4.6 Program Design

Figure 8: sequence diagram

4.7 Interface Design

Figure 9: login form

Figure 10: registration form

Figure 11: main menu

Figure 12: change password form

You might also like