E.G.S. PILLAY ENGINEERING COLLEGE (An Autonomous Institution, Affiliated to Anna University, Chennai) Nagore Post, Nagapattinam , Tamilnadu.

Transcription

1 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB 70CA0 SOFTWARE ENGINEERING METHODOLOGIES Academic Year : Programme : MCA Question Bank Year / Semester : I / II Course Coordinator : Mrs.S.Visalatchy Course Objectives. To provide an insight into the processes of software development.. To understand and practice the various fields such as analysis, design, development, testing of Software Engineering.. To develop skills to construct software of high quality with high reliability.. To apply metrics and testing techniques to evaluate the software. Course Outcomes: On completion of the course, students will be able to CO: Familiarize the basic concepts of Software Engineering and various models. CO: Model software projects into high level design using DFD,UML diagrams. CO: Perform software testing on various applications. CO: Apply various software metrics on software quality products. PART A ( Mark Questions With Key) S.No Questions Mark COs BTL UNIT I INTRODUCTION Define software engineering paradigm. K To solve actual problems in an industry, a software engineer or a team of engineers must. combine a development strategy that includes the process, methods and tools. This strategy is referred as software engineering paradigm or process model There exist various software development strategies or process models. 0. Give the difference between known risks and predictable risks. K Known Risks: That can be not covered after careful computation of the project plan, business and technical environment in which the product is being build up. Illustration: Impractical delivery rate. Predictable Risks: Extrapolated from the past project experience. Illustration: Staff turn-over. Define software prototyping. K Software prototyping is defined as a rapid software development for validating the requirements. What are the disadvantages of linear sequential model? K Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. What is the difference between systems engineering and software engineering? K System engineering It deals with all aspects of computer-based system development. It is to identify the roles of hardware, software, people, database and other system elements involved with that system which is going to be developed. Software engineering It is a part of system engineering. It is to tell the practicalities of developing and delivering useful software. 6 Write the approaches for Software process assessment. K

2 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Obtaining guidance for improving software development and test processes Obtaining an independent and unbiased review of the process Obtaining a baseline (defined as a set of software components and documents that have been formerly reviewed and accepted; that serves as the basis for further development) for improving quality and productivity of processes. 7 What are the benefits of prototyping? K. Prototyping serves as a basis for deriving system specification.. Design quality can be improved.. System can be maintained easily.. Development efforts may get reduced.. System usability can be improved. 8 What are the various rapid prototyping techniques? K. Dynamic high level language development.. Database programming.. Component and application assembly. 9 What is Software Engineering? K The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software. 0 How does Personal Software Process(PSP) differ from Team Software Process(TSP)? K The Personal Software Process (PSP) is an SEI technology that brings discipline to the practices of individual software engineers, dramatically improving product quality, increasing cost and schedule predictability, and reducing development cycle time for software. The Team Software Process (TSP) is a complementary SEI technology that enables teams to develop software-intensive products more effectively. TSP shows a team of engineers how to produce quality products for planned costs and on aggressive schedules. What is a process Framework? K Establishes foundation for a complete software process. By identifying a small number of framework activities that are applicable for all software projects regardless of their size and complexity. What are the Generic Framework Activities? K Communication. Planning. Modeling. Construction. Deployment. Define Stakeholder. K Anyone who has stake in successful outcome of project. Business managers, end users, software engineer, support people. How the process models differ from one another? K Based on flow of activities. Inter dependencies between activities. Manner of quality assurance. Manner of project tracking. Team organization and roles. Work products identify an requirement identifier What are the drawbacks of RAD model? K Require sufficient number of human resources to create enough number of teams. Developers and customers are not committed, system result in failure. Not properly modularized building component may problematic. Not applicable when there is more possibility for technical risk. UNIT II REQUIREMENT ANALYSIS Define Metrics for software. K

3 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB A software metric is a measure of software characteristics which are quantifiable or countable. Software metrics are important for many reasons, including measuring software performance, planning work items, measuring productivity, and many other uses. Mention the different types of software metrics. K. Productivity Metrics.. Quality Metrics.. Technical Metrics.. Size-Oriented Metrics.. Function oriented Metrics. 6. Human-oriented Metrics. What is the difference between verification and validation? K Verification Validation. Are we building the product right?. Are we building the right product?. Verification shows conformance with specification.. Validation shows that the program meets the customer s needs. List the common errors in verification process. K Incomplete specifications Misunderstand of customer communication Deviation from specifications Violation of programming standards Errors in data representation List out the elements of analysis model. K i. Data Dictionary ii. Entity Relationship Diagram iii. Data Flow Diagram iv. State Transition Diagram v. Control Specification vi. Process specification 6 What are the information s available in the data dictionary? K Precise definition of data elements, User names, roles and privileges, Schema objects, Integrity constraints, stored procedure, General data base structure, Space allocations. 7 Why it is difficult to gain a clear understanding of what the customer wants? K Customer requirement is gathered at particular period of time. So the customer is not able to predict the future which they are going to work. So it is difficult to gain a clear understand about what they wants. 8 What are the five distinct steps in requirement engineering? K Requirement inception Requirement elicitation Requirement elaboration Requirement analysis and negotiation Requirement specification 9 What are the non functional requirements for software? K The non functional requirements define system properties and constraints. Various properties of the system can be Reliability, response time, storage requirements. Constraints of the system can be Input and output device capability, system representations. 0 What is CSPEC? K A control specification (CSPEC) represents the behaviour of the system (at the level from which it has been referenced) in two different ways. The CSPEC contains a state diagram that is a sequential specification of behaviour. It can also contain a program activation table a combinatorial specification of behaviour. Define requirement engineering process. K Requirement engineering is the process of establishing the services that the customer requires from the system and the constraints under which it operates and is developed. What is Class Based Modelling? K

4 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB A CRC model is really a collection of standard index cards that represent classes. The cards are divided into three sections. Along the top of the card you write the name of the class. In the body of the card you list the class responsibilities on the left and the collaborators on the right. List out the basic principles of software project scheduling? K Compartmentalization. Interdependency. Time Allocation. Effort Validation. Defined Responsibilities. Defined Outcomes. Defined Milestones. What are the elements for requirement model? K Scenario-based elements. Data models Class-based elements. Behavioural elements Flow-oriented elements. What is Domain Analysis? K Software domain analysis is the identification, analysis, and specification of common requirements from a specific application domain, typically for reuse on multiple projects within that application domain UNIT III SOFTWARE DESIGN List of principles of a software design. K i. The design process should not suffer from tunnel vision. ii. The design should be traceable to the analysis model. iii. The design should exhibit uniformity and integration. iv. Design is not coding. v. The design should not reinvent the wheel. What are the characteristics of a good design? K Understanding Meaning Value Engagement Fit Emotion Define Abstraction. K Abstraction is a process of consolidating on entire set of detailed attributed by using a few central traits or even a single name to represent them. It is a tool that allows us to deal with concepts apart from particular instances or those concepts. List out the types of Abstraction? K a. Function al abstraction. b. Data abstraction. c. Control abstraction. Define Modularity. K Module is a small functional routine. It can stand on itself or it can be coupled with other application also. Modular systems incorporate collections of abstraction. A modular system consists of well-defined manageable units with well-defined interface among units. 6 How the architecture design can be represented? K Architecture design can be represented by one or more different models. They are: a. Structural Models.

5 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB b. Framework Models. c. Dynamic Models. d. Process Models. 7 What is cohesion? K Indication of relative functional strength of a module. Natural extension of information hiding. Performs a single task, requiring little integration with other components. 8 What are the different types of coupling? K a. Content Coupling. b. Common Coupling. c. Control Coupling. d. Stamp Coupling. e. Data Coupling. f. Routine Call Coupling. g. Type Use Coupling. h. Inclusion or Import Coupling. i. External Coupling. 9 What is the various design notations are there? K. Dataflow diagram.. Structure charts.. HIPO diagram.. Pseudo code. 0 What are use-cases? K A use case in software engineering is a description of a system s behavior as it responds to a request that originates from outside of that system. In other words, a use case describes who can do what with the system in question. The use case technique is used to capture a system s behavioral requirements by detailing scenario-driven threads through the functional requirements What are the different types of Cohesion? K *Coincidentally cohesive * logically cohesive *Temporal cohesion * Procedural Cohesion * Communicational cohesion Define real time system. K Real time system is a software system in which the correct functionalities of the system are dependent upon results produced by the system and the time at which these results are produced. What are the characteristics of distributed system design? K Fault-Tolerant: It can recover from component failures without performing incorrect actions. Highly Available: It can restore operations, permitting it to resume providing services even when some components have failed. Recoverable: Failed components can restart themselves and rejoin the system, after the cause of failure has been repaired. Consistent: The system can coordinate actions by multiple components often in the presence of concurrency and failure. Scalable: It can operate correctly even as some aspect of the system is scaled to a larger size. Predictable Performance: The ability to provide desired responsiveness in a timely manner. Secure: The system authenticates access to data and services. What is the importance of Documentation? K Documentation is an important part of Software Engineering. It is a viable part of Software Development process and without it, it is hard to maintain any project and the developers have to

6 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB re-invent the wheel What are the major issues of designing reuse? K The design reuse process has four major issues:. Retrieve. Reuse. Repair. Recover UNIT IV SOFTWARE TESTING Define software Testing. K Testing can be described as a process used for revealing defects in software, and for establishing that the software has attained a specified degree of quality with respect to selected attributes. What are the principles of testing the software engineer must apply while performing the software testing? K All tests should be traceable to customer requirements. Tests should be planned long before testing begins. The Pareto principle can be applied to software testing-80% of all errors uncovered during testing will likely be traceable to 0% of all program modules. Testing should begin in the small and progress toward testing in the large. Exhaustive testing is not possible. To be most effective, an independent third party should conduct testing. Distinguish black box and white box testing. K Black Box Testing. Black box testing is called behavioural testing.it examines a system functionality with testcase input and output. White Box Testing. white box testing is called glass box testing. Here the procedural details, all the logical paths, all the internal data structures are closely examined. What is meant by cyclomatic complexity? K Cyclomatic complexity is a software metric that gives the quantitative measure of logical complexity of the program V(G)=E-N+ E-Number of flow graph edges N-Number of flow graph nodes Differentiate between testing and debugging. K Testing Debugging Testing as a dual purpose Debugging or fault localization is the process of process Locating the fault or defect Reveal defects Repairing the code, and And to evaluate quality attributes Retesting the code. 6 List out the characteristics of testability of software? K Operability. Controllability. Decomposability. Simplicity. Stability. Understand ability. 7 What problems may be encountered when Top-Down Integration is chosen? K Delays are test until stubs replace with actual modules. Develop stubs that perform limited functions that simulate the actual module. Integrate the software from the bottom of the hierarchy upward. 8 What are the steps in bottom-up integration? K Low level components are combined into clusters perform specific software sub function. Driver is written to coordinate test case input and output. Cluster is tested.

7 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Drivers are removed and clusters are combined moving inward in program structure. 9 What is the objective of unit testing? K The objective of unit testing is to test the modules individually in order to detect the defect. 0 What are the steps involved in testing real time system? K *Task testing * Behavioural Testing *Inter task Testing *System Testing What is the use of drivers and stubs in testing? K A driver is a main program that accepts test case data, passes such data to the component and print relevant results. A stub or dummy subprogram uses the subordinate module s interface, may do the minimal data manipulation, prints verification of entry and returns control to the module undergoing testing. What are the errors uncovered by black box testing? K Incorrect or missing functions Interface errors Errors in data structures Performance errors Initialization or termination error Why tests are important with respect to software? K The purpose of software testing is to ensure whether the software functions appear to be working according to specifications and performance requirements. This helps in improving the overall quality of the software. What are the attributes of good test? K a. High probability of finding errors. b. Not redundant. c. Best of breed d. Neither too simple nor too complex. What are the limitations of testing? K In traceability Undesirability UNIT V SOFTWARE MAINTENANCE AND SOFTWARE METRICS What are the types of maintenance? K Corrective maintenance: maintenance for correcting the software faults Adaptive maintenance: maintenance for adapting the change in environment. Enhancement maintenance: modifying or enhancing the system to meet the new requirements Preventive maintenance: changes made to improve future maintainability. What is software configuration management? K The software configuration management is a mechanism for Identifying. Controlling. Tracking. What are the components of the cost of quality? K Quality costs. Prevention costs. Appraisal costs. What is software quality control? K Involves series of inspections reviews and tests. Used throughout software process to ensure each work product meets requirements placed

8 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB upon it. What are baseline criteria in SCM? K a) Help to control change. b) Specification or product that has been formally. c) Reviewed and agreed upon serves as basis for future development. d) That can be change only through formal change control procedures. 6 List out the elements of SCM? K Component elements. Process elements. Construction elements. Human elements. 7 What are the features supported by SCM? K Versioning. Dependency tracking and change management. Requirements tracking. Configuration Management. Audit trails. 8 What are the objectives of SCM process? K Identify all items, collectively define software configuration. Manage changes to one or more these items. Facilitate construction of different version of an application. Ensure that the software quality is maintained. 9 What do you understand by direct measure and indirect measure with respect to software? K Direct measures of the software engineering process include cost and effort applied. Direct measures of the product include lines of code (LOC) produced, execution speed, memory size, and defects reported over some set period of time. Indirect measures of the product include functionality, quality, complexity, efficiency, reliability, maintainability, and many other " abilities". 0 List out few product and process metrics. K Process metrics: Lines of code or function points per module and function, defect reported for major software function, errors found during formal technical review. Product metrics: Metrics for testing, maintenance,quality Define CASE Tools. K It is system software. Provide automated support for software process activities. Includes program used to support software process activities such as requirement analysis, system modelling, debugging and testing. What are the types of CASE Tools? K Types of CASE Tools.. Upper CASE Tools.. Lower CASE Tools. What is meant by metrics and measurement? K Metrics is the degree to which a system component or processes possesses a given attribute. The software metrics relate several measures. Eg: average no. of errors found per review. Measurement means deriving a numeric value for an attribute of a software product or process. What are the building blocks of CASE? K CASE has the following components, Environment architecture, Hardware platform, Operating system, Portability services, Integration frame work, and CASE tools Define software reliability. K Software reliability is defined in statistical terms as "the probability of failure-free operation of a

9 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB computer program in a specified environment for a specified time" PART B ( Mark Questions with Key) S.No Questions Mark COs BTL UNIT I INTRODUCTION Explain linear life cycle model in detail. Give the advantages and disadvantages of the same K Diagram for Waterfall model The model encompasses the following activities:. System/information engineering and modelling. Software requirement analysis. Design. Code generation. Testing 6. Support Advantages and disadvantages Explain in detail the spiral model with a neat sketch and discuss its merits and demerits. K It is an evolutionary software process model. Combines the elements of the linear sequential model with iterative nature of prototyping Used for the development of large scale systems and software. Spiral model diagram The task regions are: Customer communication Planning Risk analysis. Engineering. Construction and release. Customer evaluation. Explain the various prototyping approaches or prototyping models in detail. K i. Evolutionary Prototyping Objective is to deliver a working system to end user Start with the user requirements which are best understood. Diagram for Evolutionary prototyping. Advantages Accelerated delivery of the system User engagement with the system Problems Management problems Maintenance problems Contractual problems ii. Throw-away Prototyping Objective is to validate or derive the system requirements. Diagram for Throw away prototyping Start with those requirements that are not well understood. Advantages Requirements risks are very less. Problems It can be undocumented. Changes made during the software development proceed may degrade the system structure. Sometimes organizational quality standard may not be strictly applied. Discuss in detail the RAD model with a neat sketch and discuss its advantages and disadvantages. Rapid Application Development Model is the type of incremental Model. Diagram 8 K

10 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Phases include. Business modelling. Data modelling. Process modelling. Application generation.. Testing and turnover. Write in detail about Agility principles K. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.. Welcome changing requirements, even late in development. Agile processes harness change for the customer s competitive advantage.. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.. Business people and developers must work together daily throughout the project.. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers,and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 0. Simplicity the art of maximizing the amount of work not done is essential.. The best architectures, requirements, and designs emerge from self organizing teams.. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 6 Explain in detail about Industrial Extreme Programming (IXP). K Explanation about IXP Readiness assessment. Project community. Project chartering. Test-driven management. Retrospectives. Continuous learning. UNIT II REQUIREMENT ANALYSIS Discuss in detail about Requirements elicitation and analysis in requirements engineering. K The activities involved in elicitation and analysis process are: Collaborative Requirements Gathering Quality Function Deployment Normal requirements. Expected requirements. Exciting requirements. Elicitation Work Products Usage Scenarios What are the elements of Requirements model? Explain it. K Scenario-based elements with example. Class-based elements with example. Behavioural elements with example. Flow-oriented elements with example.

11 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Explain about Data Modeling concepts in requirement modeling in detail. With neat diagram. K Introduction Data Objects Data Attributes Relationships Examples with neat diagram. Create a control flow in requirement modeling with neat diagrammatic representation. K Introduction The Control Specification The Process Specification PSPEC: process password Examples with neat diagram. Describe the process and product metrics in detail. K Measures, Metrics, and Indicators Metrics in the Process and Project Domains Software Measurement Reconciling Different Metrics Approaches Metrics for Software Quality Integrating Metrics Within the Software Engineering Process Managing Variation: Statistical Quality Control Metrics for Small Organizations Establishing a Software Metrics Program 6 Discuss about classification of Metrics with neat diagram. K Halstead s Metrics Graph Theoretic Metric McClure s Complexity Metric Example with neat diagram. UNIT III SOFTWARE DESIGN Explain the set of principles for software engineering design. K The design process should not suffer from tunnel vision. The design should be traceable to the analysis model. The design should not reinvent the wheel. The design should minimise intellectual distance between the software and the problem as it exists in the real world. The design should exhibit uniformity and integration. The design should be structured to degrade gently, even with bad data, events, or operating conditions are encountered. The design should be reviewed to minimize conceptual (semantic) errors. Design is not coding, coding is not design. The design should be structured to accommodate change. The design should be assessed for quality as it is being created. Explain various design concepts in detail. K Abstraction Architecture Patterns Separation of Concerns Modularity Information Hiding Functional Independence Refinement Aspects

12 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Refactoring Object-Oriented Design Concepts Design Classes Define cohesion and coupling. Explain the various types in each of them. K Definition for Cohesion Types of Cohesion Example Definition for Coupling Types of Coupling Example Explain the software documentation in detail. K Introduction Writing a good design documentation Supporting documents Program Unit Notebooks Release Approval Internal Documentation Explain in detail about real-time and distributed system design with neat diagrammatic representation. K Real-time and Distributed System design Explanation. Example with neat Diagram for real-time system. Real-time programming Example for Distributed System with neat diagram The distributed architecture and design principles 6 Discuss in detail about software reuse. K Reuse based software engineering Benefits of reuse Requirements for design reuse Reuse Problem Designing for reuse Design with reuse is complementary to design for reusability UNIT IV SOFTWARE TESTING Explain the bottom up testing with neat diagram K Bottom up Bottom Up Testing Strategies. Bottom Up Testing Flow Diagram. Advantages and disadvantages of Bottom Up Testing. Explain the bottom up testing with neat diagram K Bottom up Bottom Up Testing Strategies. Bottom Up Testing Flow Diagram. Advantages and disadvantages of Bottom Up Testing. Explain in detail about Unit Testing with neat diagram K Unit Testing Advantages and disadvantages of Unit Testing Unit Testing Life Cycle Unit Testing Techniques. Explain Functional Testing verses structural Testing Coding. K Functional Testing Merits of Functional Testing Demerits of Functional Testing structural Testing Coding

13 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Merits of structural Testing Coding Demerits of Functional Testing Explain Functional Testing in detail. K Functional Testing Advantages and disadvantage of Functional Testing Functional Testing Workflow 6 6 Explain structural Testing Coding in detail. K Structural Testing Coding Advantages and disadvantage of structural Testing Coding Structural Testing Coding workflow 6 UNIT V SOFTWARE MAINTENANCE AND SOFTWARE METRICS How to measure the Process and Product attributes in detail. K Product Vs Process Process Metrics and software process improvement. Project Metrics Example with neat diagram. Explain in detail about Direct and Indirect measure with examples. K Size Oriented Metrics Function-Oriented Metrics Feature Point Metrics Metrics for Software Quality Integrating Metrics within Software process Describe about Software Reliability. K Software Reliability Metrics Software Safety Mistake-Proofing Software ISO 9000 Quality Standards The SQA Plan Discuss in detail about Software Quality Assurance. K Software Quality Assurance. SQA Group Activities Software Reviews Cost impact of software defects Formal Technical Reviews Statistical Quality Assurance Six Sigma for software Engineering Explain in detail about Software Configuration Items with neat diagram. K The SM repository The Role of the Repository General Features and Content SCM Features 6 What is the Need for SCM? Explain it in detail with example. K A SCM Scenario Elements of a configuration Management System Baselines. PART C (0 Mark Questions with Key) S.No Questions Mark COs BTL UNIT I INTRODUCTION

14 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Case study for Project Plan and Software Requirements Specification. 0 K Project Plan Explanation Explain in detail about Extreme Programming (XP) in Agile model with example. 0 K XP Values The XP Process Industrial XP The XP Debate UNIT II REQUIREMENT ANALYSIS Develop a use case for Safe Home control panel. 0 K Identify the Actors The basic use case for system activation to homeowner uses the control panel 7 Use case Diagram The following template for detailed descriptions of use cases: Use case: Initiate Monitoring Primary actor: Homeowner. Goal in context: To set the system to monitor sensors when the homeowner leaves the house or remains inside. Preconditions: System has been programmed for a password and to recognize various sensors. Trigger: The homeowner decides to set the system, i.e., to turn on the alarm functions. Scenario:. Homeowner: observes control panel. Homeowner: enters password. Homeowner: selects stay or away. Homeowner: observes read alarm light to indicate that SafeHome has been armed Exceptions:. Control panel is not ready: homeowner checks all sensors to determine which are open; closes them.. Password is incorrect (control panel beeps once): homeowner re enters correct password.. Password not recognized: monitoring and response subsystem must be contacted to reprogram password.. Stay is selected: control panel beeps twice and a stay light is lit; perimeter sensors are activated.. Away is selected: control panel beeps three times and an away light is lit; all sensors are activated. Priority: Essential, must be implemented When available: First increment Frequency of use: Many times per day Channel to actor: Via control panel interface Secondary actors: Support technician, sensors Channels to secondary actors: Support technician: phone line Sensors: hardwired and radio frequency interfaces Explain in detail about Cost Estimation with example. 0 K Expert Judgment 6 Delphi estimation technique 8 Work Breakdown Structure(WBS) 6 UNIT III SOFTWARE DESIGN Explain in detail about data Flow Oriented Modeling with neat diagrammatic representation. 0 K

15 Nagore Post, Nagapattinam 6 00, Tamilnadu. COE/08/QB Creating a control flow model The Control Specification(CSPEC) The Process Specification(PSPEC) Class-Responsibility-Collaborator(CRC( Modeling Discuss in detail about Software Architecture with diagrammatic representation. 0 K Why Architecture is important Architectural Styles and Patterns Refining the Architecture into components Assessing alternative architectural designs Analyzing Architectural design Describing instantiations of the system Architectural Complexity Architectural Description Language Mapping dataflow into a Software Architecture Transform mapping Transaction mapping Functional Independence UNIT IV SOFTWARE TESTING Case study for Testing Techniques. 0 K Testing Types with explanation 0 Test Case Design Example with diagram. Explain in detail about Software Testing fundamental with example. 0 K Software Testing Fundamentals Testing Objectives Testing Principles 0 Testability UNIT V SOFTWARE MAINTENANCE AND SOFTWARE METRICS Explain in detail about CASE Taxonomy. 0 K Explanation about CASE Tools Types. Configuration Management Features need by CASE Tools Describe about SCM Task in detail with diagram. 0 K Identification of Objects in the Software Configuration 6 Version Control Change Control Configuration Audit Status Reporting