Literature Review contains a complete picture of the related work done including critical analysis of existing software architecture evaluation methods / frameworks used to ensure quality of service in software architecture. It also consists of the limitations of existing models and provides motivation for further research in the same field. This chapter has been categorized into following four sub-sections according to the specific aspects of research domain. 2.1 Quality Attributes and the Quality Model An important issue in software development today is quality. Nonfunctional characteristics of a component or a system are called quality attribute.
A systems analyst researches the problems and plans solutions for these problems. He also recommends systems and software at the functional level and also coordinates the development in order to meet the business or other requirements. For good system analyst skills required are 1. The ability to learn quickly. 2.
It is the blueprint, or plan, or template, that describes the details of an object. A class is the blueprint from which the individual objects are created. Class is composed of three things: a name, attributes, and operations (Codeproject.com,
Object diagrams was function as describing the static structure of a system at a particular time. Then, in collaboration diagrams, they shows interaction between objects and describe both the static structure and the dynamic behaviour of a system. For sequence diagrams, it shows interaction among classes in term of an exchange of messages over time. For activity diagram, it give a view of dynamic of a system by modelling the flow of control from activity to activity. For component diagrams, it explain about the organization of physical software component (run-time code, executables, and source code).
We can consider software engineering as a three dimensional model where each dimension is concerned with a particular aspect. The first dimension contains tools and techniques required to develop software. The second covers all management principles required to organize software projects successfully. And third holds all non-functional attributes (security, portability, interoperability) required to develop an application. These are sometimes referred to as the ‘-ilities’ Another important aspect software engineering is people.
Introduction: At a technical level, software engineering fundamental activities are Software specification, software development, software validation, and software evolution. The analysis model is a set of models and first technical representation of the system. Several methods have been proposed for analysis modeling. The two common and well known approaches are as follows: Structural analysis is a building model which determines the data ( their attributes and relationships) and the processes that transforms the data. Object-oriented analysis based upon the concepts of Classes and their inter-relationships.
PRABHU RAGHU RAM ANGAJALA J00504557 Research Paper Part1 Detailed Annotated Outline of research paper 1. INTRODUCTION The software engineering ontology defines information for the exchange of semantic project information and is used as a communication framework. In the area of computer science, Ontology represents the effort to formulate an exhaustive and rigorous conceptual schema within a given domain. Several Ontology languages such as Resource Description Framework (RDF), Web Ontology Language, DARPA Markup Language and Ontology Interchange Language (OIL) are available. 2.
The third concept in the object model is the Encapsulation which is the concept of including processing or behavior with the object instances defined by the class. Encapsulation allows code and data to be packaged together. The third database model would be the UML model that stands for Unified Modeling Language used for writing software blue prints. The UML can be used to visualize, specify, construct, and document the artifacts of a software-intensive system. (Safari Tech Books Online, 2002, chap.
Structural Diagrams consist of diagrams such as Class Diagrams, Component Diagrams, and Deployment Diagrams. Behavioral Diagrams consist of diagrams such as Activity Diagrams, Communication Diagrams and Timing Diagrams. Structural Diagrams show what the software is made up of, while Behavioral Diagrams show what the software is doing step by step. Above is an example of a Class Diagram. It consists of three sections.
This set has an architecture known as instruction set architecture (ISA). An instruction set architecture (ISA) is the interface between the computer's software and hardware and also can be viewed as the programmer's view of the machine. It defines the codes that a central processor reads and acts upon. An interface is a shared boundary across which two separate components of a computer