Page 70 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 70

Principles of Software Engineering                              Deepak Mehta, Lovely Professional University



                   Notes                    Unit 4: Introduction to Validation, Metrics



                                   CONTENTS

                                   Objectives
                                   Introduction
                                   4.1   Function Point and Quality Metrics
                                       4.1.1   Function Point Analysis
                                       4.1.2   Software Quality Metrics
                                   4.2   Software Architecture
                                       4.2.1  Meta-architecture
                                       4.2.2   Conceptual Architecture

                                       4.2.3   Logical Architecture
                                       4.2.4   Execution Architecture
                                   4.3   Architecture Views
                                       4.3.1   Architecture Documentation
                                   4.4   Architecture Styles
                                       4.4.1   Client/Server Architectural Style
                                       4.4.2   N-Tier/3-Tier Architectural Style

                                       4.4.3   Shared Data Architecture
                                   4.5  Summary
                                   4.6  Keywords
                                   4.7   Review Questions
                                   4.8   Further Readings

                                 Objectives

                                 After studying this unit, you will be able to:

                                    •  Explain the function point and quality metrics
                                    •  Describe the software architecture
                                    •  Discuss the architecture views

                                    •  Define the architecture styles

                                 Introduction

                                 The process of provided that confirmation that the software and its connected products satisfy
                                 system requirements allocated to software at the end of each life-cycle action, solve the accurate
                                 problem  (e.g.,  correctly  model  physical  laws,  implement  business  rules,  use  proper  system
                                 assumptions), and satisfy intended use and user needs.
                                 A more generic definition of corroboration is “the steps and the process needed to ensure that
                                 the system configuration, as designed, meets all requirements initially specified by the customer.”



        64                                LOVELY PROFESSIONAL UNIVERSITY
   65   66   67   68   69   70   71   72   73   74   75