Software reuse of a system consists of four processes: development
Software reuse of a system consists of four processes: development management support and reuse of reusable assets (building blocks).
2) Component technology A component is an interchangeable physical part of a software system that encapsulates an implementation body (which fulfils a function) and provides a set of methods for implementing the interface. In order to assemble the components developed by different software manufacturers on different hardware and software platforms into an application system the interoperability between the components of heterogeneous platforms must be addressed
5.53K
views
Five system views: logical view
Five system views: logical view process view implementation view deployment view and use case view.
2.10 Components and Software Reuse A component (component) is a relatively functionally independent unit of software with reusable value. In the object-oriented approach a component consists of a set of objects containing a collection of collaborative classes that work together to provide a system functionality.1) Software reuseReusability is the extent to which a system and/or its components can be reused in other systems.
5.51K
views
The UML has three basic constructs
These are things relationships and diagrams. Public mechanisms are public UML methods for achieving specific goals and include four main types of specification (detailing) modification public classification (generic division) and extension mechanisms. Rules the semantic rules that UML uses to describe things are named things relations and diagrams respectively.
5.51K
views
2) Unified Modelling Language Unified Modelling Language (UML)
2) Unified Modelling Language Unified Modelling Language (UML)
is a well-defined easy to express powerful and universally applicable modelling language. Its scope is not limited to supporting object-oriented analysis and design but also supports the whole process of software development starting with requirements analysis.The structure of UML: The structure of UML consists of the basic building blocks the rules that govern how these building blocks are put together (the architecture) and a number of mechanisms that apply to the whole of UML.
5.55K
views
Inheritance is a central idea that distinguishes object-oriented methods from other methods.
Encapsulation: The unit of encapsulation in an object-oriented system is the object and information can only be exchanged between objects through interfaces. Messages: Messages are the means of communication between objects where one object requests a service by sending a message to another object. Polymorphism: Polymorphism means that the same operation can be interpreted differently when applied to different objects and produce different execution results
5.52K
views
an object name an attribute and an operation (method).
Classes: A class is a collection of objects with the same properties and the same operations. Each class generally has instances; a class without instances is an abstract class. Inheritance: Inheritance is a mechanism by which different classes in a hierarchical association of a class share properties and operations. For two classes A and B if class A is a subclass of class B then class B is a generalisation of class A.
3.46K
views
Each of these CMMI models has two representations namely phased and continuous.
2.9 Object-Oriented Approach mainly examines the basic concepts of object-oriented data hiding UML and building blocks. 1) Basic concepts Object-oriented approach includes object-oriented analysis object-oriented design and object-oriented programming. Object: An object is a set of attributes and a wrapper for dedicated operations on this set of attributes. An object can typically consist of three parts
5.48K
views
2) CMMI is not limited to software
2) CMMI is not limited to software but covers software engineering systems engineering integrated product development and systems procurement.
5.5K
views
(1) CMM is divided into: initial level
(1) CMM is divided into: initial level repeatable level defined level managed level and optimised level.
3.48K
views
The ISO/IEC9126 software quality model has been adopted by China's national standards
GB/T16260 - 2002 Information Technology Software Product Evaluation Quality Characteristics and Guidelines for Their Use. 2.8 Software Process Improvement Software Process Capability Maturity Model (CapabilityMaturityModel CMM) and Capability MaturityModelIntegration ( CapabilityMaturityModelIntegration CMMI)
5.47K
views
Software quality assurance refers to the planned and organised activities carried
Software quality assurance refers to the planned and organised activities carried out to ensure that a software system
or software products fully meet the required quality these activities are planned and organised throughout all phases of software production i.e. the entire life cycle. There are two types of software quality characteristics metrics: predictive and acceptance. Commonly used international software quality models are ISO/IEC9126 and the McCall model.
3.47K
views
From the perspective of application scope it can be divided into holistic and local methods.
1) Cleanroom method cleanroom software engineering method is a formal method which can produce high-quality software. Cleanroom method is a strict software engineering method. It is a software process model that emphasizes mathematical verification of correctness and certification of software reliability. Its objectives and results have a very low error rate which is difficult or impossible to achieve by using non formal methods.
1.65K
views
Modeling tools software development tools
Modeling tools software development tools software testing tools and project management tools. 2.1 software development method software development method is a subject whose research object is software development method. From different angles software methodology can be classified as follows: from the perspective of development style it can be divided into top-down and bottom-up development methods; From the nature it can be divided into formal and non formal methods
2.05K
views
3) Software architecture
Software architecture definition typical architecture software architecture design method software architecture analysis and evaluation software middleware. 4) Object oriented system analysis and Design: basic concept of object-oriented unified modeling language (UML) visual modeling object-oriented system analysis object-oriented system design.
2.04K
views
1) Software engineering knowledge
Software requirements analysis and definition software design testing and maintenance software reuse software quality assurance and quality evaluation software configuration management software development environment and software process management. 2) Technical knowledge of software components: components and their importance in information system projects common component standards (COM / DCOM / COM + CORBA and EJB).
1
view
G2E (government to employee)
G2B (government to business government to citizen) G2C (government to citizen) 3) e-commerce B2B (business to business business to enterprise) B2C (businesstocustomer business to individual) C2C (customertocustomer individual to individual) Chapter 2 basic knowledge points of system development
1.64K
views
Customer Relationship Management (CRM)
Supply chain management (SCM) business intelligence (BI) and enterprise portal (EP) can be divided into three categories: Information Portal (EIP) knowledge portal (EKP) and Application Portal (EAP) 2) e-government G2G (government to government)
3
views