Prepara tus exámenes y mejora tus resultados gracias a la gran cantidad de recursos disponibles en Docsity
Gana puntos ayudando a otros estudiantes o consíguelos activando un Plan Premium
Prepara tus exámenes
Prepara tus exámenes y mejora tus resultados gracias a la gran cantidad de recursos disponibles en Docsity
Prepara tus exámenes con los documentos que comparten otros estudiantes como tú en Docsity
Los mejores documentos en venta realizados por estudiantes que han terminado sus estudios
Estudia con lecciones y exámenes resueltos basados en los programas académicos de las mejores universidades
Responde a preguntas de exámenes reales y pon a prueba tu preparación
Consigue puntos base para descargar
Gana puntos ayudando a otros estudiantes o consíguelos activando un Plan Premium
Comunidad
Pide ayuda a la comunidad y resuelve tus dudas de estudio
Descubre las mejores universidades de tu país según los usuarios de Docsity
Ebooks gratuitos
Descarga nuestras guías gratuitas sobre técnicas de estudio, métodos para controlar la ansiedad y consejos para la tesis preparadas por los tutores de Docsity
The software process activities module in the ingles técnico aplicado a ingeniería course at universidad autónoma de occidente. The focus is on requirements analysis and modeling, including domain analysis, reusability, and object-oriented approaches. The document also covers scenario-based modeling, user interface design, and software testing.
Qué aprenderás
Tipo: Guías, Proyectos, Investigaciones
1 / 4
Esta página no es visible en la vista previa
¡No te pierdas las partes importantes!
Summarize: Module #3 Software Process Activities
Software Process Activities (Summarize) The objective is to reach a written agreement that describes the functionality of the software to be developed. The end product of this activity is often referred to as a specification and forms the basis for all the development activities that follow. It turns out that the activities at this stage of the development life cycle are among the most difficult, but perhaps the most important. Bringing modeling and design tools into this phase is not unusual. Requirements analysis and modeling The focus of this activity is to define the operational characteristics of the software and has three main objectives: to provide the following: • basis for software design • Definition of the operating system that can be used for system validation once softwares development completed. The following sub-activities are identified with requirements analysis and modeling: Domain analysis Reusability is an important goal in software development, as it reduces development costs, increases reliability, and reduces development time. Domain analysis is the process of identifying patterns that can be reused. Analysis modeling sometimes begins with identifying all the data objects to be processed in the system and the relationships between these objects. Data modeling is used for large database and information systems applications. The object-oriented (OO) approach to analysis represents the latest "paradigm shift" in analysis methodology and is embodied by the Java language at the implementation stage. • Customers can understand OO models without programming knowledge, facilitating the important initial phases of communication. • OO languages promote code reuse and therefore programmer productivity • OO design and analysis methods adapt to change The OO approach is based on modeling the problem domain using classes and objects. The goal of object-oriented analysis is to design all associated classes and methods that are appropriate for the system being developed. The Unified Modeling Language (UML) has been developed for the modeling and development of object-oriented (OO) systems.
User interface design A common mistake of software projects is spending too little time communicating with the user. It's easy for software experts to fall into the subconscious trap of "knowing what's good for the user." • Put the user in control • Reduce user memory load • Make the interface consistent Software testing After coding the software system into a deliverable product, testing strategies are used to validate the system requirements. The testing strategies for conventional design software differ somewhat from those for object-oriented systems. Conventional software: unit testing focuses on execution paths through component program logic with the goal of maximizing error detection through path coverage; whereas integration tests generally involve input and output values. The thread-based approach tests the set of classes that respond to a certain input or system event. After unit and integration testing, the entire system is tested according to customer requirements. This final testing phase is generally called a validation test and includes alpha and beta testing. Alpha testing is done at the developer's site and beta testing is done later at the end-user sites. The final release of the software is scheduled after beta testing is complete. Product Metrics for Software The use of objective measures of software development products as an empirical measure of quality is controversial in the software engineering community. Some say that our lack of basic understanding of the software justifies delaying the development and use of such metrics. However, there are many metrics available to help evaluate and guide source code analysis, design, development, and testing. Analysis - Overall system size metric defined as a function of the information in the analysis model. Source code: length metric defined in terms of lines of code (LOC).
