The Evolving Role of Software The Evolving Role of Software The Evolving Role of Software The Evolving Role of Software. Factors Contributing to the Software Crisis Factors Contributing to the Software Crisis Factors Contributing to the Software Crisis Factors Contributing to the Software Crisis.
Y2K problem
The 4-digit date format, like 1964, was shortened to 2-digit format, like
Reasons
The Space Shuttle Some software bugs Some software bugs Some software bugs Some software bugs. A random group of programmers applied this system to the fuel dump module and other modules.
Seventeen additional, previously unknown problems surfaced!
However, there are desperate calls for a silver bullet, something to reduce software costs as quickly as computer hardware costs. That's why building software is always difficult and there is inherently no silver bullet.
Computer programs and associated documentation
Documentation consists of different types of manuals. Documentation consists of different types of manuals. Documentation consists of different types of manuals. Documentation consists of different types of manuals.
Operating Procedures
User Manuals
Operational Manuals
System Overview Beginner’s Guide
Installation Guide
System
Software products can be developed for a specific customer or can be developed for a general market.
Software engineering is an engineering discipline that deals with all aspects of software production. At the first conference on software engineering in 1968, Fritz Bauer defined software engineering as "The creation and use of sound engineering principles to obtain economically developed software that is reliable and runs efficiently on real machines." .
Useful life phase
Wear out phase
Writing a programConstructing a bridge
Software Real Time
Embedded Software
Artificial
Intelligence Personal
Business Software
Software Myths (Management Perspectives Software Myths (Management Perspectives) Software Myths (Management Perspectives) Software Myths (Management Perspectives. Software Myths (Software Myths) Customer Perspectives (Software Myths Customer Perspectives (Software Myths customer perspectives (Software myths customer perspectives.C.
Dependency Order
People
- Software is
- Which is not a product metric?
- Which is NOT a process metric?
- Effort is measured in terms of
- UML stands for
- An independently deliverable piece of functionality providing access to
- Infrastructure software are covered under
- During software development, which factor is most crucial?
- Program is
- The term module used during design phase refers to
- Software consists of
- Why is primary goal of software development now shifting from producing good quality software to good quality maintainable software?
- List the reasons for the “software crisis”?Why are CASE tools not normally able to control it?
- What is software crisis? Was Y2K a software crisis?
- What is the significance of software crisis in reference to software engineering discipline
- How are software myths affecting software process? Explain with the help of examples
- State the difference between program and software. Why have documents and documentation become very important
- What is aim of software engineering? What does the discipline of software engineering discuss?
- Define the term “Software engineering”. Explain the major differences between software engineering and other traditional engineering disciplines
- What is software process? Why is it difficult to improve it?
- Write down the major characteristics of a software. Illustrate with a diagram that the software does not wear out
- What are the components of a software? Discuss how a software differs from a program
- Discuss major areas of the applications of the software
- Differentiate between the following
- What is software metric? How is it different from software measurement
- Discuss software process and product metrics with the help of examples
- What is productivity? How is it related to effort. What is the unit of effort
- Differentiate between module and software component
- Distinguish between generic and customized software products. Which one has larger share of market and why?
- Describe the role of management in software development with the help of examples
- What are various factors of management dependency in software development. Discuss each factor in detail
- What is more important: Product or process? Justify your answer
Explain the major differences between software engineering and other traditional engineering disciplines. between software engineering and other traditional engineering disciplines. Illustrate with a diagram that the software does not wear out. diagram that the software does not wear out.
Can independent certification agency provide a fair playing
Certification is an employee-initiated improvement process that improves proficiency in quality assurance methods and techniques.
ISO 9000 SEI-CMM
Have largest potential market
Require thorough labour intensive preparation of most of the items on the DO-178B support list
Require fewer support item and 2. Less taxing on company resources
- What is software certification? Discuss its importance in the changing scenario of software industry
- What are different types of certifications? Explain the significance of each type & which one is most important for the end user
- What is the role of third party certification in component based software engineering? Why are we not able to stabilize the component based software
- Why customer is only interested in product certification? Discuss any product certification techniques with their generic applicability
RTOS (real-time operating system) is the real-time operating system certification and marked as "LinuxOS-178". Weyukar rightly said: “For Component Based Software Development (CBO) to revolutionize software development, developers must be able to produce software significantly cheaper and faster than they could otherwise, even though the resulting software meets the same kind of high reliability standards while still being easy to use. Bill Council has also expressed his views as follows: “Currently there is some evidence that component-based software engineering (CBSE) is revolutionizing software development, and there are many reasons to believe.
Third-party certification is a method to ensure that software components meet well-defined standards, based on this certification reliable assemblies of components can be built. Explain the importance of each type and which one is most important to the end user. The goal of software engineering is to provide models and processes that lead to the production of well-documented maintainable software in a manner that is predictable.
The period of time that begins when a software product is designed and ends when the product is no longer available for use.
Build Code
Suitable for small programming exercises of 100 or 200 lines. Unsatisfactory for software of any reasonable size. This model is easy to understand and reinforces the idea of 'define before design' and 'design before code'. They are effective in situations where the requirements are precisely defined and there is no confusion about the functionality of the end product.
In general, the phases occur in the same order as in the waterfall model, but they can be performed in several cycles. Usable product is released at the end of each cycle, with each release providing additional functionality.
Requirements specification
Architectural design
Implementation and unit testing
Integration and testing
The requirements specification was
The developers understood it in
This is how the problem was
This is how the problem is
This model differs from the iterative improvement model in that it does not require a usable product at the end of each cycle. The prototype may be a usable program, but is not suitable as the final software product. The development of a prototype may incur additional costs, but the total costs may turn out to be lower than for a similar system developed using the waterfall model.
Barry Boehm realized this and went to great lengths to incorporate the "project risk" factor into a life cycle model. An important feature of the spiral model is that each phase is completed with a review by the people interested in the project (designers and programmers). The advantage of this model is the wide range of options to accommodate the good features of other life cycle models.
The spiral model has a number of issues that need to be resolved before it can become a universally applicable life cycle model.
Definition of objectives
Planning &
Initial operational
Release of the Software
Initial development Cycle
Evolution Cycle
Continue till the product is retired
Based on characteristics of requirements Based on characteristics of requirements Based on characteristics of requirements based on characteristics of requirements.
RADSpiral
- Spiral Model was developed by
- Which model is most popular for student’s small projects?
- SDLC stands for
- Build and fix model has
- SRS stands for
- Waterfall model is not suitable for
- If requirements are easily understandable and defined,which model is best suited?
- If requirements are frequently changing, which model is to be selected?
- If user participation is available, which model is to be chosen?
- If limited user participation is available, which model is to be selected?
- If project is the enhancement of existing system, which model is best suited?
- Which one is the most important feature of spiral model?
Based on Development Team Status Based on Development Team Status Based on Development Team Status Based on Development Team Status. Limited user participation The user has no. previous experience of participating in similar projects Users are experts. Based on project type with associated risk based on project type with associated risk based on project type with associated risk based on project type with associated risk.
If the project is to improve the existing system, which model is most appropriate. a) Waterfall model (b) Prototype model (c) Iterative improvement model (d) Spiral model.
SDLC
- The development is supposed to proceed linearly through the phase in
- Unified process is maintained by
- Who is not in the team of Unified process development?
- How many phases are in the unified process?
- The outcome of construction phased can be treated as
- What do you understand by the term Software Development Life Cycle (SDLC)? Why is it important to adhere to a life cycle model while
- What is software life cycle? Discuss the generic waterfall model
- List the advantages of using waterfall model instead of adhoc build and fix model
- Discuss the prototyping model. What is the effect of designing a prototype on the overall cost of the project?
- What are the advantages of developing the prototype of a system?
- Describe the type of situations where iterative enhancement model might lead to difficulties
- Compare iterative enhancement model and evolutionary process model
- Sketch a neat diagram of spiral model of software life cycle
- As we move outward along with process flow path of the spiral model, what can we say about software that is being developed or maintained
- How does “project risk” factor effect the spiral model of software development
- List the advantages and disadvantages of involving a software engineer throughout the software development planning process
- Explain the spiral model of software development. What are the limitations of such a model?
- Describe the rapid application development (RAD) model.Discuss each phase in detail
- Compare the waterfall model and the spiral model of software development
- What is the role of user participation in the selection of a life cycle model?
- Write short note on “status of development team” for the selection of a life cycle model?
- Discuss the selection process parameters for a life cycle model
- What is unified process? Explain various phases along with the outcome of each phase
- Describe the unified process work products after each phase of unified process
- What are the advantages of iterative approach over sequential approach?
- Why do we feel that characteristics of requirements play a very significant role in the selection of a life cycle model?
Why is it important to adhere to a lifecycle model while developing a large software product.
What not How
Requirements Engineering is the disciplined application of proven principles, methods, tools, and notations to describe the intended behavior of a proposed system and its associated constraints. The problem formulation can provide an overview of the existing system and broad expectations for the new software system.
TYPES OF INTERFACES
Is cancellation of a project a bad news?
How do we cancel a project with the least work?
CONDUCT A FEASIBILTY STUDY
It is the only method that we know
It is our favorite method for all situations
We understand intuitively that the method is effective in effective customer developer partnership
Interviews
Entry level personnel 2. Middle level stakeholder
Possible benefits
Satisfied with current policies
Any requirement of data from other system 9. Any specific problems
Any additional functionality
Most important goal of the proposed development
Brainstorming Sessions
Facilitated Application specification Techniques (FAST)
Arrange a meeting at a neutral site
Establish rules for participation
Informal agenda to encourage free flow of ideas
Appoint a facilitator
Prepare definition mechanism board, worksheets, wall stickier
Participants should not criticize or debate
Part of environment that surrounds the system
Produced by the system
Used by the system
List of constraints B. Functions
Performance criteria
- Every participant presents his/her list 2. Combine list for each topic
- Discussion
- Consensus list
- Sub teams for mini specifications 6. Presentations of mini-specifications
- Quality Function Deployment
- Identify stakeholders 2. List out requirements
- Degree of importance to each requirement
- The Use Case Approach
- Introduction
- Flow of events
- Basic Flow
- Alternative Flows
- Identify all users
- Create a user profile for each category of users including all roles of the users play that are relevant to the system
- Create a use case for each goal, following the use case template maintain the same level of abstraction throughout
- Structure the use case
Use case diagrams are graphical representations that can be broken down to further levels of abstraction. A use case is initiated by a user with a specific goal in mind and completes successfully when that goal is met. Use Case captures who (actor) does what (interaction) with the system, for what purpose (goal), without dealing with the internals of the system.
Business rules should be listed for basic and information flow as special requirements in the use case narrative. These rules will also be used for writing test cases. Create a user profile for each category of users, including all roles of the users relevant to the system. Create a use case for each goal, following the use case template, maintain the same level of abstraction throughout the template, maintain the same level of abstraction throughout the use case.
Use cases are about "what" the system is, not "how" the system will be designed.
Use case diagram for Result Management System
Maintain Student Details
Maintain Subject Details
Maintain Result Details
Login
Generate Result Reports
Administrator/DR
Maintain student Details
Login
Generate Result Report
- Introduction : This use case describes how a user logs into the Result Management System
- Actors : (i) Data Entry Operator
- Alternate Flows
- Invalid name & password
- Special Requirements
- Use case Relationships
- Introduction : Allow DEO to maintain student details
- Pre-Conditions: DEO must be logged onto the
- Post-conditions : If use case is successful, student information is added/updated/deleted from the system
- Basic Flow : Starts when DEO wishes to add/modify/update/delete Student information
- Add a student
- Update a student
- Delete a student
- Alternative flows
- Student not found
- Update Cancelled
- Delete cancelled
- Special requirements None
- Use case relationships None
If the player enters an invalid username and/or password in the basic stream, the system displays an error message. If the use case is successful, the student information is added/updated/deleted from the system. data is added/updated/deleted from the system. The system asks the DEO to specify the function he wants to perform (Add/Update/Delete). ii) One of the sub-flows will be executed after obtaining the information.
The system retrieves and displays student information. iii) The DEO makes the desired changes to the student data. iv) After the changes, the system updates the student record with the changed data. me). The system asks the DEO to provide the student ID. ii) DEO enters student ID. The system prompts the DEO to confirm the deletion of the student. iv) DEO approves deletion. in).
When updating a student or deleting a student substream, if a student with specified_id does not exist, the system displays an error message. The DEO can enter a different ID or cancel the operation.
Maintain Subject Details
- Introduction
- Actors : DEO
- Preconditions : DEO must be logged onto the
- Post conditions
- Add a Subject
- Update a Subject
- Delete a Subject
- Alternative Flow
- Subject not found
- Update Cancelled
- Delete Cancellation
- Special Requirements
- Use Case-relationships
If the use case succeeds, the subject information is added, updated or deleted from the system. otherwise, the system state is unchanged. The use case starts when the DEO wants to add, change and/or delete subject information from the system. I). The system requests the DEO to specify the function he/she would like to perform ie. ii) When the DEO provides the required information, one of the subflows is executed.
If DEO selected “Delete-a-subject”, then “Delete-a-subject”. i) The system will request the DEO to access the. The system will prompt the DEO to enter subject_id. ii) DEO enters the subject_id. When updating a topic subflow, if the data entry operator decides not to update the topic information, the update occurs.
If in delete-a-subject sub-flow, the DEO decides not to delete subject, the delete is canceled, and the basic flow is restarted from the beginning.
Maintain Result Details
- Introduction
- Actor
- Pre Conditions
- Post Conditions
- Basic Flow
- Add Marks Records
- Delete Marks records
This use case starts when the DEO wants to add, update and/or delete tags from the system. i) DEO to specify the function. ii) Once the DEO has provided the information, one of the subflows is executed.
DEO makes the following entries
- Update Marks records
The System requests DEO to enter the record_id
DEO makes changes
Record is updated
- Compute Result
- Alternative Flow
- Record not found
- Delete Cancelled
- Special Requirements
- Use case relationships
- Introduction
- Actors
- Post Conditions
- Basic Flow
- View result enrollment number wise
- Alternative Flow
- Record not found
- Special Requirements None
- Use Case relationships None
If a student has achieved more than 50% in a subject, the associated credit points are awarded to that student. iii). If in update or delete marks subflow, marks with specified ID number do not exist, the system displays an error message. If in Delete Marks, DEO decides not to delete marks, the deletion is canceled and basic flow is restarted at the.
You can view the results using the course code and/or registration number. Use case starts when student, teacher or someone else wants to view the result. User to enter the registration number. ii) System retrieves the grades of all credit-bearing subjects.
Generate Report
- Introduction
- Actors
- Post conditions
- Basic Flow
- Alternative Flows
- Record not found
- Special Requirements None
- Use case relationships None
The use case starts when DR wants to generate reports. ii) The system retrieves the information views. iii) DR takes printed reports.
