---
# System prepended metadata

title: Software Engineering Periodical
tags: [MCA II]

---

# Software Engineering Periodical

###### tags: `MCA II`

## which document is used as a contact document among stack holders involve in software engineering process, by taking example explain it?

The software requirements document (also called software requirements specification or SRS) is an official document of what should be implemented. It's also used as a contract between the stakeholders and the software developers. It should include both; user and system requirements.

For an example we can take a hypothetical software project we need to undertake for the database management for an airline company. Before staring the project we need to establish the basis for an agreement between the engineers and the airline company on how the software product should function. The role can be played by the marketing and development divisions. For this a standard documentation can be implemented which makes rigorous assessment of requirements before more specific system design on later stages. Its goal is to reduce later redesign.


### wikipedia

Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers on how the software product should function (in a market-driven project, these roles may be played by the marketing and development divisions). Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules.[1] Used appropriately, software requirements specifications can help prevent software project failure.[2]

The software requirements specification document lists sufficient and necessary requirements for the project development.[3] To derive the requirements, the developer needs to have clear and thorough understanding of the products under development. This is achieved through detailed and continuous communications with the project team and customer throughout the software development process. 


.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.

.
.
.
.
.
.
.
.


.
.
.
.
.
.
.


.


## _3.b.b._ Y2K problem of software crisis

Y2K is a numeronym for the year 2000 software problem. Until the 1990s many computer programs were designed to abbreviate four-digit years as two digits in order to save memory space. These computers could recognize “98” as “1998” but would be unable to recognize “00” as “2000,” because it would interpret it to mean 1900. It was a major problem because such a misreading would lead to software and hardware failures in computers used in such important areas as banking, utilities systems, government records, and so on, with the potential for widespread problems on and following January 1, 2000.


___
I love you soooooo much meri kavyaaaaaa :hugging_face: :kissing_closed_eyes: 