0% found this document useful (0 votes)
7 views22 pages

Detailed Software Design Overview

The document describes the detailed design of a job portal software system. It outlines the modular decomposition components including Admin, Aspirants, and Employers modules. For each module, it describes the inputs, procedures, I/O interfaces, and outputs for functions like login, view jobs/aspirants, send/view feedback, and view accounts. The overall purpose is to plan the internal logic and design of each module to satisfy system requirements specified in earlier documents.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views22 pages

Detailed Software Design Overview

The document describes the detailed design of a job portal software system. It outlines the modular decomposition components including Admin, Aspirants, and Employers modules. For each module, it describes the inputs, procedures, I/O interfaces, and outputs for functions like login, view jobs/aspirants, send/view feedback, and view accounts. The overall purpose is to plan the internal logic and design of each module to satisfy system requirements specified in earlier documents.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

CHAPTER – 5

DETAIL DESIGN
5. DETAILED DESIGN
5.1 Introduction
The purpose of the design phase is to plan a solution of the problem specified by the
requirements document. This phase is the first step in moving from the problem domain to
the solution domain. In other words, starting with what is needed; design takes us towards
how to satisfy the needs. The design of the system is perhaps the most critical factor affecting
the quality of the software; it has a major impact on the later phases, particularly testing and
maintenance.
The design activity often results in three separate outputs- Architecture Design, High Level
Design and Detailed Design. Architecture focuses on looking at a system as a combination of
many different components, and how they interact with each other to produce the desired
results. The High-Level Design identifies the modules that should be built for developing the
system and the specifications of these modules. At the end of system design all the major data
structures, file formats, output formats etc., are also fixed. In detailed design, the internal
logic of each of the modules are specified.
The design process for the software systems often has two levels. At the first level, the focus
is on deciding which modules are needed for the system, the specifications of these modules
and how the modules should be interconnected. This is what is called the System Design or
the Top-Level Design. In the second level, the internal design of the modules, or how the
specifications of the module can be satisfied is decided. This design level is often called
Detailed Design. Detailed design essentially expands the system design to contain a more
detailed description of the processing logic and data structures so that the design is
sufficiently complete for coding.
\
5.1.1 Applicable Documents
The Detailed Design refines the System Design document hence the first applicable
document here is system design. We also refer the data structures. Hence the second
applicable document is database design.

5.2 Structure of the Software Package


The various functional components used are
 Admin module
 Aspirants Module

Apply
for jobs
 Employer Module
5.3 Modular Decomposition Components

5.3.1 Admin
[Link] Login
a) Input: Email ID, Password.
b) Procedure details:

Start

Enter email and password

Verification False Incorrect


(Email,Psw) Email/Password

True

Display Home Page

Stop

[Link] Login
c) I/O interface: Graphical user interface(Form) for admin to enter the email and password.
d) Output: The email ID and Password is verified. If correct ,the admin gain authorization
into the Admin Page.
[Link] Add New Admin
a) Input: Email, username, password.
b) Procedure details:

[Link] Add New Admin


c) I/O interface: Graphical user interface(Form) for admin to enter the required details.
d) Output: The email ID and Password is verified. If correct, new admin will be created.
[Link] View all users and Manage
a) Input: After successful Login into admin panel.
b) Procedure details:

View account
details

[Link] View all users and Manage


c) I/O interface: Graphical user interface.
d) Output: Admin can view the details of users and also, Admin can manage their accounts.
[Link] Send Response
a) Input: Email- id and feedback
b) Procedure details:

Start

Send Response

False
Validation

Sent successfully

Stop

[Link] Send Response

c) I/O interface: All the users of the application have interface to give feedback.
The admins can view the feedback and give Response if necessary.
d) Output: The Response for feedback Will be sent.
[Link] View feedback
a) Input: Email- id and feedback
b) Procedure details:

Start

Open Menu

False
Feedback No feedback
available

True

Feedback Display

Stop

[Link] View feedback

c) I/O interface: The admin can view the feedback.


d) Output: The feedback stored In the database is displayed.
5.3.2 Aspirants
[Link] Login
a) Input: Email, password
b) Procedure details:

Start

Enter email/password

False Incorrect
Verification
Email/Password

True

Display Home Page

Stop

[Link] Login

c) I/O interface: Graphical user interface for Aspirants to enter the email and password.
d) Output: The email and password are verified. If correct, the Aspirants gain authorization
into the web application.
[Link] View and Apply
a) Input: Successful Login
b) Procedure details:

[Link] View and Apply

c) I/O interface: Graphical user interface for Aspirants to search and sort their dream jobs.
d) Output: Successfully Applied for dream job.
[Link] Send feedback
a) Input: The user needs to input feedback description and email.
b) Procedure details:

Start

Give feedback

False
Validation

Inserted successfully

Stop

[Link] Send feedback

c) I/O interface: All the users of the application have interface to give and view feedback.
The admins can view the feedback
d) Output: The given feedback are stored in the database and Response will be sent back.
[Link] View Response
a) Input: Feedback and Email
b) Procedure details:

Start

Open Menu

False
Feedback No feedback
available

True

Display Response

Stop

[Link] View Response

c) I/O interface: The admin will view the feedback and Give Response and Aspirants can
view the responses.
d) Output: The Response is displayed.
[Link] Account
a) Input: Already Provided while Registering(Username, Email and other details).
b) Procedure details:

[Link] Account
c) I/O interface: The Aspirants can view their account details.
d) Output: The Account Details will be displayed.
5.3.3 Employers
[Link] Login
a) Input: Email, password
b) Procedure details:

Start

Enter email/password

False Incorrect
Verification
Email/Password

True

Display Home Page

Stop

[Link] Login

c) I/O interface: Graphical user interface for Employers to enter the email and password.
d) Output: The email and password are verified. If correct, the Employers gain authorization
into the web application.
[Link] View Jobs Posted by Employer
a) Input: New Jobs
b) Procedure details:

[Link] View Jobs Posted by Employer

c) I/O interface: Graphical user interface for Employers to view the jobs.
d) Output: If there are Jobs then it will be displayed else an empty page will be displayed.
[Link] View Aspirants
a) Input: Job Application
b) Procedure details:

[Link] View Aspirants

c) I/O interface: Graphical user interface for Employers to view the aspirants who applied
for their jobs.
d) Output: If there are Aspirants who applied for Jobs then it will be displayed else an empty
page will be displayed.
[Link] Send feedback
a) Input: The user needs to input feedback description and email.
b) Procedure details:

Start

Give feedback

False
Validation

Inserted successfully

Stop

[Link] Send feedback

c) I/O interface: All the users of the application have interface to give and view feedback.
The admins can view the feedback
d) Output: The given feedback are stored in the database and Response will be sent back.
[Link] View Response
a) Input: Feedback and Email
b) Procedure details:

Start

Open Menu

False
Feedback No feedback
available

True

Display Response

Stop

[Link] View Response

c) I/O interface: The admin will view the feedback and Give Response, The Employers can
view the Response.
d) Output: The Response is displayed.
[Link] Account
a) Input: Already Provided while Registering(Username, Email and other details).
b) Procedure details:

[Link] Account
c) I/O interface: The Employers can view their account details.
d) Output: The Account Details will be displayed.
[Link] Add Jobs
a) Input: New Jobs
b) Procedure details:

[Link] Add Jobs

c) I/O interface: The Employers can add new Jobs along with basic description including
eligibilty, work life, slary and many more.
d) Output: New Job with all details will be displayed.

You might also like