Software Engineering

When computer software succeeds- when it meets the needs of the people who use it,when it performs flawlessly over a long period of time,when it is easy to modify and even easier to use- it can change things for the better.But when software fails-when users are dissatisfied,when it is error prone,when it is difficult to change and even harder to use-bad things can and do happen.We all want to build software that makes things better,avoiding the bad things that lurk in the shadow of failed efforts.To succeed,we need discipline when software is designed and built.We need an engineering approach.

Friday, April 1, 2011

Important Questions


SYBSC IT                                                                                                                      Subject: Software Engineering      
                                                                                                                              
Important Questions
NOTE:
a)      Give an Example Wherever Possible.
b)      Draw Diagrams Wherever Necessary.
c)       Write in point form. Essays will not be entertained.
d)      Any question can be asked on the following topics.
                                     Love, 
                                                 P.S   


  INTRODUCTION

1.      1.   Attributes of a good software
2.       Different costs involved in software engineering
3.       Software process model
4.       CASE (Computer- Aided Software Engineering)                             
5.       What is software? What is software Engineering?    
6.       Key challenges facing Software Engineering
7.       Principles of Code of Ethics    
        
PROCESS MODELS

8.       Waterfall Process Model
9.       Incremental Development Model
10.   Testing Process Model
11.   Evolutionary Development Model

PROJECT MANAGEMENT

12.   Project plan structure 
13.   Different types of project plans
14.   Risk Management
15.   Draw the activity network for the following problem
16.   Why does a manager have to appoint a less than ideal team sometime? 
        
REQUIREMENTS

17.   Problems of using natural language.
18.   Different types of non- functional requirement.
19.   Discover the ambiguities or omissions in the following statement of requirements for part of a ticket issuing system. An automated ticket issuing system sells rail tickets. Users select their destination, and input a credit card and a personal identification number. The rail ticket is issued and their credit card account charged with its cost. When the user presses the start button, a menu display of potential destinations is activated along with a message to the user to select a destination. Once a destination has been selected, users are requested to input their credit card. It’s validity is checked and the user is then requested to input a personal identifier. When the card transaction has been verified, the ticket is issued. 
20.   Write a set of non- functional requirements for the ticket issuing system described above, setting out its expected reliability and its response time.     
    
SYSTEM ENGINEERING

21.   UML Class diagram
a.       Student Class
b.      Rectangle Class
22.   What is System Modeling? What are the factors an engineer should consider to construct a System Model?         
23.   Context Model  



SYSTEM MODELS and VERIFICATION AND VALIDATION

24.   DFD
25.   Difference between Verification and Validation.
26.   Multiple Inheritance Model
27.   Two techniques within Verification and Valiation.

TESTING

28.   Path Testing
29.   White Box Testing
30.   Defect Testing
31.   Black Box Testing
Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)