A Concise Introduction to Software Engineering has 10 ratings and 0 reviews. An introductory course on Software Engineering remains one of the hardest su. A Concise Introduction to Software Engineering. Author: Pankaj Jalote, Indian Institute of Technology Delhi. Publisher: Springer, , ISBN: xxxxx. An introductory course on Software Engineering remains one of the hardest subjects to teach largely because of the wide range of topics the.

Author: Voodookus Tygogar
Country: Colombia
Language: English (Spanish)
Genre: Travel
Published (Last): 17 January 2012
Pages: 274
PDF File Size: 7.72 Mb
ePub File Size: 6.98 Mb
ISBN: 275-9-36980-671-7
Downloads: 66029
Price: Free* [*Free Regsitration Required]
Uploader: Negal

This need for changes requires that methods for development embrace change and accommodate it efficiently. This causes a communication gap between the parties involved in the de- velopment project. An important part of the specification is the system behavior in abnormal situations, like invalid input which can occur in many ways or error during computation.

The development approach used in an iteration has some unique practices. What are the main differences between a student software and industrial-strength software? Security requirements are becoming increasingly important. Often we tend to teach too many concepts and topics in an introductory course resulting in shallow knowledge and little insight on application of these concepts.

Pentru Movila marked it as to-read Mar 01, By suitably staffing the teams, the duration of each of the three phases—analysis and design, build, and deployment—can be made approximately equal. English Choose a language for shopping. The subprocesses of requirements, de- sign, coding, testing, etc.

Any software project involves the use of engineering and project jalotw ment. The goal of this book is to introduce to the students a limited number of concepts and practices which will achieve the following two objectives: Use cases specify the functionality of a system by specifying the behavior of the system, captured as interactions of the users with the system.

A Concise Introduction to Software Engineering

Assume that each resource can do any task. What are the key outputs during an iteration in a project following an iterative development model? Why is maintenance needed for software, when software has no physical components that can degrade with age? What other items do customers buy after viewing this item? What are the different attributes of software quality?


For example, the use case diagram of UML provides an overview of the use cases and actors in the system and their depen- dency. We will in a later chapter discuss in detail the project planning phase.

However, they are a general method for describing the interaction of a system even non-IT systems. Many of these do not concern software engineering, though they do impact software development.

Software Processes in Figure 2. The capability to be understood, learned, and used. A primary actor is the main actor that initiates a use case UC for achieving a goal, and whose goal satisfaction is the main objective of the use case.

That is, the final quality delivered and productivity achieved depends on the skills of the people involved in the software project, the processes people use to perform the different tasks in the project, and the tools they use.

The exact definition of what is considered a defect will clearly depend on the project or the standards the organization developing the project uses typically it is the latter.

Much of the book discusses the different phases of a development process and the subprocesses or methodologies used for executing these phases. With 2 months as the completion time, the productivity of the student will be lines of code LOC per person-month.

A Concise Introduction to Software Engineering by Pankaj Jalote

Software engineering is an softwwre part of studies in computer science and consequently foundational knowledge is critical to all students in the field. That is, a new iteration commences before the system produced by the current iteration is released, and hence development of a new release happens introuction parallel with the development of the current release. Consequently, things like user interfaces are rarely modeled, whereas they fre- quently form a major component of the SRS.


He may document the infor- mation or build some models, and he may do some brainstorming or thinking about what the system should concis. The iterative enhancement model. Published September 29th by Springer first published January 1st Consider the problem of counting people in a room versus taking a census of a country.

For example, if there is a formula for computing the output, it should be specified. Most industrial-strength software systems tend to be large and complex, requiring tens of thousands of lines of code. Some of these subgoals may be achieved by the system itself, but they may also be treated as separate use cases executed by supporting actors, which may be another system.

A defect could be some problem in spftware software that causes the software to crash or a problem that causes an output to be not properly aligned or one that misspells some word, etc.

The use of registered names, trademarks, etc. There are a few key reasons for its increasing popularity. Consequently, only those features are included in the prototype that will have a valuable return from the user experience.

Due to this connection with an object-oriented approach, use cases are sometimes viewed as part of an object-oriented approach to software development. Primary ac- The main actor for whom a use case is initiated and whose tor goal satisfaction is the main objective of the use case.

Amazon Music Stream millions of songs. Return to Book Page.