CHAPTER 5

Details Of Design Working and Process

5.1 Introduction
5.2 System Analysis
5.2.1 Introduction to system analysis
5.2.2 Software Design approach
5.3 Block Diagram
5.4 System Architecture
5.5 Timeline Chart
5.6 Cost Estimation
5.7 Feasibility
5.8 DFD and UML
5.1 Introduction

A network security monitoring system (NSMS) is a set of tools and processes

designed to detect, analyze, and respond to security threats in a computer network.
The main goal of an NSMS is to improve network security by providing continuous
monitoring of network activity and detecting any suspicious or unauthorized activity.

The web app can be used to track the activity of employees or children to ensure that
they are not accessing inappropriate content or wasting company time. It can also be
used to detect and prevent cyber-attacks, such as malware and phishing attempts. With
its advanced features, a network monitoring system app can help improve network
performance and maintain a secure and efficient network environment.

5.2.1 Introduction to system analysis

It is a process of collecting and interpreting facts, identifying the problems, and

decomposition of a system into its components. System analysis is conducted for the
purpose
of studying a system or its parts in order to identify its objectives. It is a problem
solving
technique that improves the system and ensures that all the components of the system
work
efficiently to accomplish their purpose. Analysis specifies what the system should do

5.2.2 Software design approach

Iterative process starts with a simple implementation of a subset of the software

requirements and iteratively enhances the evolving versions until the full system is
implemented. At each iteration, design modifications are made and new functional
capabilities are added. The basic idea behind this method is to develop a system
through repeated cycles (iterative) and in smaller portions at a time (incremental)

Iterative models are often used in software development projects, where they help to
reduce the risks associated with developing complex systems. They allow for early
detection and resolution of issues, reduce the time and cost of development, and
provide an opportunity for stakeholders to provide feedback throughout the
development process. Additionally, the iterative approach allows for changes to be
made at any stage of the project, based on the feedback received, making it a flexible
and adaptable methodology.
5.3 Block Diagram
5.4 System Architecture

5.5 Time-Line Chart

A timeline chart is an effective way to visualize a process using chronological order.

Since details are displayed graphically, important points in time can be easy seen and
understood. Often used for managing a project’s schedule, timeline charts function as
a sort of calendar of events within a specific period of time.
A Timeline chart is constructed with a horizontal axis representing the total time span
of the project, broken down into increments (for example, days, weeks, or months)
and a vertical axis representing the tasks that make up the project (for example, if the
project is outfitting your computer with new software, the major tasks involved might
be: conduct research, choose software, install software). Horizontal bars of varying
lengths represent the sequences, timing, and time span for each task. Using the same
example, you would put "conduct research" at the top of the vertical axis and draw a
bar on the graph that represents the amount of time you expect to spend on the
research, and then enter the other tasks below the first one and representative bars at
the points in time when you expect to undertake them.
The bar spans may overlap, as, for example, you may conduct research and choose
software during the same time span. As the project progresses, secondary bars,
arrowheads, or darkened bars may be added to indicate completed tasks, or the
portions of tasks that have been completed. A vertical line is used to represent the
report date.
Timeline charts give a clear illustration of project status, but one problem with them is
that they don't indicate task dependencies - you cannot tell how one task falling
behind schedule affects other tasks.
5.6 COST ESTIMATION

Total number of weeks= Weeks in 5th semester + Weeks in 6th semester

= 14 + 13
=27

Total number of weeks= 27 weeks.

Total number of hours = Total num. of weeks * Num. of hours spent per week
=27*15
=405

Total number of hours= 405 hours.

Cost Estimation= Total number of hours * Cost per hour

=405 *25

Cost Estimation= Rs. 10,125

Total Cost Estimation of Proposed System= Rs. 10,125