Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

se project 3 and 4 and, Cheat Sheet of Computer Science

it is a se project giveb in ip university hope it helps

Typology: Cheat Sheet

2022/2023

Uploaded on 01/09/2023

rushilkhanna_
rushilkhanna_ 🇮🇳

1 document

1 / 52

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-
110036
(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute)
INDEX
S.
No
Experiment Description Pa
g
e
N
o.
Experimen
t Date
Submissio
n Date
Remark
s
1
To write the problem statement of
WEATHER FORECASTING
SYSTEM.
22/9/2022
2
To do the requirement analysis and
develop Software Requirement
Specification Sheet for WEATHER
FORECASTING SYSTEM.
6/10/2022
3
To perform the function-oriented
diagram: Data Flow Diagram (DFD)
and Structured chart.
13/10/2022
4
To perform the user’s view analysis
for the suggested system: Use case
diagram.
20/10/2022
5
To draw the structural view diagram
for the system: Class diagram, object
diagram.
10/11/2022
6
To draw the behavioral view
diagram
: State-chart diagram, Activity
diagram
17/11/2022
7
To perform the behavioral view
diagram for the suggested system:
Sequence diagram,
Collaboration diagram
8/12/2022
8
To perform the implementation
view diagram: - Component
diagram for the System
22/12/2022
28/12
1
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34

Partial preview of the text

Download se project 3 and 4 and and more Cheat Sheet Computer Science in PDF only on Docsity!

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute)

INDEX

S.

No Experiment Description Pa g e N o. Experimen t Date Submissio n Date Remark s 1 To write the problem statement of WEATHER FORECASTING SYSTEM.

2 To do the requirement analysis and develop Software Requirement Specification Sheet for WEATHER FORECASTING SYSTEM.

3 To perform the function-oriented diagram: Data Flow Diagram (DFD) and Structured chart.

4 To perform the user’s view analysis for the suggested system: Use case diagram.

5 To draw the structural view diagram for the system: Class diagram, object diagram.

6 To draw the behavioral view diagram : State-chart diagram, Activity diagram

7 To perform the behavioral view diagram for the suggested system: Sequence diagram, Collaboration diagram

8 To perform the implementation view diagram: - Component diagram for the System

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute) EXPERIMENT – 1 AIM: - To write the problem statement of WEATHER FORECASTING SYSTEM. REQUIREMENTS: -

  1. SOFTWARE REQUIREMENT – Microsoft Word
  2. HARDWARE REQUIREMENT – Computer, Keyboard, Mouse, CPU THEORY: - Weather forecasting is the prediction of the state of the atmosphere for a given location using the application of science and technology. This includes temperature, rain, cloudiness, wind speed, and humidity. Weather warnings are a special kind of short-range forecast carried out for the protection of human life. Weather warnings are issued bye governments throughout the world for all kinds of threatening weather events including tropical storms and tropical cyclones depending upon the location. The forecast may be short-range or Long-range. It is a very interesting and challenging task. This module provides a basic understanding of the purpose and scope of weather forecasts, the basic principles, and the general models developed for forecasting. Introduction: Weather forecasting means the prediction of the weather through the application of the principles of physics, supplemented by a variety of statistical and empirical techniques. PROBLEM STATEMENT: - If it is true, as every scientist believes, that subsequent atmospheric states develop from the preceding ones according to physical law, then it is apparent that the necessary and sufficient conditions for the rational solution of forecasting problems are the following: 1.A sufficiently accurate knowledge of the state of the atmosphere at the initial time. 2.A sufficiently accurate knowledge of the laws according to which one CONCLUSION: -

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute) beginners establish their place and survive in the market. Furthermore, it also focuses on the overall overview of the market for the upcoming period of 2021 to 2027. This has proved to be of a great help to the entrepreneurs. This in-detail market study is highly based on the information received from interviews with the leading executives, research and innovative resources. Overview: The global weather forecasting system and solutions market size was valued at USD 2. billion in 2016. It is expected to post a CAGR of 7.1% over the forecast period. These systems help enterprises in gaining real-time insights into atmospheric conditions, which in turn, enables enterprises to carefully plan all weather-sensitive operations to ensure security, sustainability, safety, and cost efficiency. Factors such as growing sea and air transportation, increasing stringency of norms pertaining to environmental protection, and high dependency on rainfall for water supply are among the key trends stimulating market growth. Drawbacks of existing System:

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute) Proposed system:  User registration: Administrator permit user for registration, companies can also do registration.  Inserting the details: user and companies have to insert their details.  Updating the details: As time user and companies have to update their details.  Event Details: Administrator update the weather.  Recruitment Process: Every 3-hour updating weather. Functional Requirements:

  1. New user requirements: When user want to get advantage of this Application, they have to first Register themselves by providing their details. After completion of registration a User ID and Password will be provided to the user. They can use that id and password for login to application and see the weather detail.
  2. User log in: A registered user can login to the system by using his User ID and Password provided after registration. After Successful login home page is shown. In home page user can see details and see the weather location to give system.
  3. Searching: User can search company by,  Technology  Location
  4. Updating Schedule details: Weather forecasting Advantages Disadvantages  Farmers can know when to plant or harvest their crops  People can choose where and when to take their holidays to take advantages of good weather  Surfers known when large waves are expected  Regions can be evacuated if hurricanes or floods are expected  Aircraft and shipping rely heavily on accurate weather forecasting  Weather is extremely difficult to forecast correctly  It is expensive to monitor-so many variables from so many sources  The computers needed to perform the millions of calculations necessary are expensive  The weather forecasters get blamed if the weather is different from the forecast

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute) Database server: SQL Development tool: Eclipse, sublime text Programming Language: java, HTML, CSS Communication interface:  This website supports all types of web browsers.  User will be informed about placement process via uploading dashboard by administrator.  Selected candidates will be informed for interview via mail by company. Performance requirements: Response Time: Response time will be less than 1s. Security: The details of the students will be kept secured by providing password facility and while updating details after OTP validation. Efficiency: All the details of the students will be kept updated. Design Constraints:  Software must be flexible so that user can easily update their details and can easily go through placement process.  The system must be able to manage the details of the users very efficiently.  Using this system placement process can be carry out from anywhere so that this application is also useful in pandemic situations like corona.  All the users have provided their important details so that software must provide the security of their data. Non-Functional Requirements:

  1. Security Requirements: Every Login Time Verification by OTP. OTP and password verification while updating details.
  2. Database Requirements:

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT Hamidpur,Delhi-

(An iso 9001:2008 certified, AICTE approved & GGSIP university affiliated institute) To store, maintain and access details of the thousands of students and also companies. Performance Requirements: Sorting facilities for quick access. preliminary schedule and budget:  We gave 1 month to discuss about software, cost, deadlines, risk analysis etc.  2 months for requirement gathering from user and then by analyzing that we made SRS document and verified that from user.  2 months for Data collection like details of different companies which wanted to involve.  3 months to Design software according to user requirements and.  2 months for implementation and testing for final product.  The budget will depend on the teams that which resources they are going to use like database, Reviews of the experts and risk analyzers may increase cost. Appendices:

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) EXPERIMENT – 3 AIM: - To perform the function-oriented diagram: Data Flow Diagram (DFD) and Structured chart. REQUIREMENTS: - 1.SOFTWARE REQUIREMENT – Microsoft Word 2.HARDWARE REQUIREMENT – Computer, Keyboard, Mouse, CPU THEORY: -

1. Data Flow Diagram (DFD) A Data Flow Diagram (DFD) is a traditional visual representation of the information flows within a system. A neat and clear DFD can depict the right amount of the system requirement graphically. It can be manual, automated, or a combination of both. It shows how data is entered and leaves the system, what changes the information, and where data is stored. The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be used as a communication tool between a system analyst and any person who plays a part in the order that acts as a starting point for redesigning a system. The DFD is also called as a data flow graph or bubble chart. 1.1 The following observations about DFDs are essential:  All names should be unique. This makes it easier to refer to elements in the DFD.  Remember that DFD is not a flow chart. Arrows is a flow chart that represents the order of events; arrows in DFD represents flowing data. A DFD does not involve any order of events.  Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box in a DFD, suppress that urge! A diamond-shaped box is used in flow charts to represents decision points with multiple exists paths of which the only one is taken. This implies an ordering of events, which makes no sense in a DFD.  Do not become bogged down with details. Defer error conditions and error handling until the end of the analysis.

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) 1.2 Standard symbols for DFDs are derived from the electric circuit diagram analysis and are shown in fig: Symbols Name Function → Data flow Used to connect processes to each other, to sources or sinks, to arrow head indicates direction of data flow. Process Performs some transformation of input data to yield output data. Source or Sink (external entity) A source of system inputs or sink of system outputs. Data Store A repository of data , the arrow heads indicate the net input and net output to store. ● Circle: A circle (bubble) shows a process that transforms data inputs into data outputs. ● Data Flow: A curved line shows the flow of data into or out of a process or data store. ● Data Store: A set of parallel lines shows a place for the collection of data items. A data store indicates that the data is stored which can be used at a later stage or by the other processes in a different order. The data store can have an element or group of elements. ● Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or sink of system outputs.

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) Fig: Level-1 DFD 1.4 DFD of WEATHER FORECASTING SYSTEM 1.4.0 Context DFD of WEATHER FORECASTING SYSTEM Fig: Context level DFD

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) 1.4.1 Level-0 DFD of WEATHER FORECASTING SYSTEM Fig: Level-0 DFD 1.4.2 Level-1 DFD of WEATHER FORECASTING SYSTEM Fig: Level-1 DFD

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) 2.1 Symbols used in construction of structured chart

1. Module It represents the process or task of the system. It is of three types as shown in below figure. ● Control Module: A control module branches to more than one sub module. ● Sub Module: Sub Module is a module which is the part (Child) of another module. ● Library Module: Library Module are reusable and invokable from any module. 2. Conditional Call It represents that the control module can select any of the sub modules on the basis of some condition as shown in below figure. 2. Loop (Repetitive call of module) It represents the repetitive execution of a module by the sub module. A curved arrow represents a loop in the module.

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) All the sub modules covered by the loop repeat execution of the module.

3. Data Flow It represents the flow of data between the modules. It is represented by directed arrow with an empty circle at the end. 4. Control Flow It represents the flow of control between the modules. It is represented by a directed arrow with a filled circle at the end.

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) 2.4 Structure Chart of WEATHER FORECASTING CONCLUSION: - ● Level – 0 and Level – 1 Data Flow Diagram (DFD) for WEATHER FORECASTING SYSTEM have been drawn successfully. ● Structure Chart for WEATHER FORECASTING SYSTEM have been drawn successfully

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT

Hamidpur, Delhi-

(An iso 9001:2008 certified,AICTE approved & GGSIP university affiliated institute) EXPERIMENT – 4 AIM: - To perform the user’s view analysis for the suggested system: Use case diagram. REQUIREMENTS: -

  1. SOFTWARE REQUIREMENT – Microsoft Word, Umbrello
  2. HARDWARE REQUIREMENT – Computer, Keyboard, Mouse, CPU THEORY: - According to the UML specification a use case diagram is “a diagram that shows the relationships among actors and use cases within a system.” Use case diagrams are often used to: ● Provide an overview of all or part of the usage requirements for a system or organization in the form of an essential model or a business model ● Communicate the scope of a development project ● Model your analysis of your usage requirements in the form of a system use case model Use case models should be developed from the point of view of your project stakeholders and not from the (often technical) point of view of developers. There are guidelines for: ● Use Cases ● Actors ● Relationships ● System Boundary Boxes 1. Use Cases A use case describes a sequence of actions that provide a measurable value to an actor. A use case is drawn as a horizontal ellipse on a UML use case diagram.
  3. Use Case Names Begin With a Strong Verb
  4. Name Use Cases Using Domain Terminology
  5. Place Your Primary Use Cases In The Top-Left Corner Of The Diagram
  6. Imply Timing Considerations By Stacking Use Cases.