text stringlengths 2 2.33k | source stringclasses 826
values |
|---|---|
Soft skills such as communication and problem-solving skills are important to being successful in the role of a software engineer. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
A software engineering process framework is used to define the software process model or SDLC model that will be used to create a software solution. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Most SDLC models use phases or standard framework activities. The four common phases are inception, elaboration, construction, and deployment. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
SDLC models differ in terms of the rigidity and number of software engineering actions they specify need to be completed as part of the software development process. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
One major category of process models is the traditional process models, which are usually prescriptive, sequential, and may not be suitable for projects with rapidly changing requirements. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
A second major category of process models is the Agile process models, which are less rigid, allowing for activities to skipped or accelerated to deliver a project solution faster and integrating user input early in the process. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
In software development, developers use software architecture to view and evaluate the system as a whole before moving to component design. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
In addition to the generic framework activities, there are other activities that crosscut the entire software development process but arenât part of the main building steps themselves, such as communication and training, risk management and planning, software configuration and content management, software quality man... | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Software engineers should understand the various models and how they differ. Some of the popular software process models include the waterfall model, V-model, incremental model, prototyping model, spiral model, Unified Process model, and Agile Process models (such as Scrum and DevOps, among others). | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Testing is a critical part of building successful software solutions. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
To ensure quality, software goes through various levels of testing, such as unit testing, integration testing, and system testing, and it is subject to different testing approaches, such as acceptance testing, usability testing, stress testing, performance testing, and security testing. Each test serves an important fu... | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Test-driven development in a process in which developers write unit tests before they write code. While counterintuitive, this can help clarify requirements, facilitate early bug detection, and even improve design and code quality. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Whereas unit testing focuses on the various units or pieces within a software solution, system testing focuses on the complete and fully integrated software product. Systems can be manual or automated. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Acceptance testing is used to determine that the software system works as was specified in the requirements. Taking place after system testing, this is typically done by the customer, client, or other end user of the software. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Usability testing tests the user interface by gaining feedback from a small group of users who are representative of the target audience. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
When developing software, developers use tools such as compilers, debuggers, profilers, integrated development environment (IDEs), version control systems, and bug tracking systems. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
To resolve problems that commonly occur in the development of a software system, developers use reusable solutions called architectural patterns and design patterns. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Refactoring is a technique for restructuring an existing piece of code without changing its functionality. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Open-source software is provided with source code. Examples of open-source projects are Linux, Android, NetBeans IDE, Eclipse IDE, and the C# programming language. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Whether you simply use software or create software, it is important to understand licensing so that you know what you can or cannot do with the software. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Software engineers should abide by a code of ethics that guides the work that they do and the solutions that they produce. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
The ACM/IEEE-CS Joint Task Force produced a Software Engineering Code of Ethics and Professional Practices that states that software engineers shall commit themselves to making the analysis, specification, design, development, testing, and maintenance of software a beneficial and respected profession. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
Software engineering and the development of software solutions is evolving. As technology changes, so do some of the ways software is coded. | https://openstax.org/books/introduction-computer-science/pages/9-summary |
abstract representation : used to hide background details | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
Agile EA Management (AEAM) : methodology used for software development and project management; AEAM breaks individual projects into smaller pieces to be easier to manage, which speeds up design processes and produces quality products | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
Agile software development : interactive approach to software development that delivers value to the customers | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
ArchDev (SecOps) : example of an Accelerated Architecture-Driven Digital Transformation Process, which helps companies proactively embed stakeholder interest and sustainability into the companyâs digital growth | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
archetype : abstraction (similar to a class) that represents one element of system behavior | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
architectural style : abstract patterns located at the top of the pattern hierarchy; they capture sets of characteristics and features that make a structure identifiable | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
architecture continuum : represents a structure of building blocks to reuse the architecture assets that conform to a language pattern | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
Architecture Development Method (ADM) : detailed step-by-step process for developing or changing an enterprise architecture | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
business process : series of steps performed by a group of stakeholders to achieve an enterprise concrete goal | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
business service choreography : example of business architecture pattern that focuses on the observed sequence of messages exchanged by peer services when performing a unit of work | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
business service orchestration : generalization of business service composition and a pattern used to describe the sequencing of business services | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
cloud : storage solution that holds data, software, and services that run on the Internet instead of on a local computer | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
component : encapsulated part of a software system, which has an interface and serves as a building block for the structure of a subsystem | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
data architecture : design framework that structures how data is collected, stored, managed, and utilized within a system | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
enabler : supports the activities needed to extend the architectural runway to provide future business functionality | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
enterprise architecture (EA) : conceptual blueprint that defines the structure and operation of organizations | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
enterprise architecture framework (EAF) : ensures that enterprise solutions are in alignment with the evolving vision and strategy of the organizations that use these solutions to operate and conduct day-to-day business | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
enterprise architecture management (EAM) : helps guide the adoption of technology stacks and corresponding implementation frameworks | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
framework : implementation-specific skeletal subsystem for design work | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
governance : processes and organizational structures that ensure compliance with the reference architecture | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
idiom : phrase or expression whose meaning cannot be inferred from the literal definitions of its individual words, but instead is understood through common usage within a language | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
IT automation : process of creating systems to reduce manual intervention | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
IT context management : dynamic IT process that uses data in one application to point to data resident in a separate application | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
IT governance : process that ensures the effective and efficient use of IT in enabling an organization to achieve its goals | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
meta-framework : framework in more detail | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
metamodel : evolving outlines for capabilities and relationships | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
method : set of repeatable processes that ensure consistent and controlled execution of the architecture | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
microservice : approach to building a software solution as a set of small services that may be deployed locally or on the cloud | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
pattern catalog : collection of patterns organized according to specific characteristics and according to how the relationships between them are defined | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
pattern hierarchy : architectural styles, architectural patterns, and design patterns | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
pattern language : connected view of how to apply one pattern in the presence of another | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
patterns management : series of patterns that create an organization chart for developing software | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
principles : core rules that guide the design and implementation of the reference architecture | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
requirements model : model that describes the problem set, establishes the context, and identifies the system of forces that hold sway, such as design quality attributes | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
road map : used to guide an organization with planning and achieving business goals over time through technology | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
singleton : design pattern that restricts the instantiation of a class and ensures that only one instance of the class exists | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
software engineering : detailed study of engineering to design, develop, and maintain software | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
software stack : collection of independent components or subsystems such as operating systems, protocols, databases, architectural layers, and function calls that work together to support the execution of an application | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
solution architecture management : managing, designing, and describing the solution engineering in relation to specific business problems | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
solutions architect manager : responsible for building teams, establishing relationships, setting strategy, and measuring and delivering results for any problem or opportunity the enterprise may face | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
subsystem : set of collaborating components that perform a given task included in software systems, and it is a separate entity within a software architecture | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
The Open Group Architecture Framework (TOGAF) : EA methodology and framework used by leading organizations to improve business efficiency | https://openstax.org/books/introduction-computer-science/pages/10-key-terms |
A pattern documents a recurring problem/solution pairing within a given context. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Patterns can be used to construct architectures at various levels of scope to guarantee specific properties. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Patterns are classified as design or implementation centric. Design-centric patterns are organized in a pattern hierarchy that includes architectural styles, architectural patterns, and design patterns. Implementation-centric pattern hierarchy includes implementation styles, implementation patterns, and idioms. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
In patterns terminology, styles are named collections of architectural decisions that are applicable in a given solution context, constrain architectural decisions that are specific to a solution within that context, and elicit beneficial qualities in each resulting system. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of organizations. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Design modeling provides a variety of different views of the system like architecture plans for the enterprise. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
The architecture may appear in different levels of focus from a top-down standpoint (i.e., enterprise, portfolio, or project). | https://openstax.org/books/introduction-computer-science/pages/10-summary |
A pattern catalog is a collection of patterns that are organized according to specific characteristics and the relationships between them are defined. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Implementation patterns are typically specific to technology stacks that are selected as part of the specialization of a solution design. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Patterns management comprises a series of patterns that create an organization chart for developing software. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Enterprise architecture (EA) is a comprehensive, well-defined approach of business planning to utilize information technology to meet the objectives of the business vision by aligning business and technology strategies. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Enterprises focus on activities that allow them to meet their current and future objectives. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
The enterprise IT strategy is based on a collective set of principles that form a consistent framework for technology decision-making and reflect a level of consensus among key stakeholder technology groups. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Business and technology executives are responsible for managing IT projects so that they achieve division-wide and company-wide objectives by engaging with the enterprise architects. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Aligning business and technology strategies is typically difficult to do on an ongoing basis because of the lack of alignment with enterprise-driven initiatives. Enterprise architecture helps align business and technology strategies. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
There are many enterprise architecture frameworks, such as TOGAF, Gartner, C4ISR, CORBA, FEA, and Zachman. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
The Open Group Architecture Framework (TOGAF) is an EA methodology and framework used by leading organizations to improve business efficiency. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Architecture Development Method (ADM) is a detailed step-by-step process for developing or changing an enterprise architecture as well as a content framework to help drive greater consistency in the outputs that are created when using the ADM. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
ADM defines the TOGAF approach for establishing processes linked with enterprise architecture. It provides a recursive and tested process development business architecture; every phase of the ADM is iterative in nature to develop an enterprise-wide architecture. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
ADM phases are Preliminary Phase, Architecture Vision, Business Architecture, Information System Architecture, Technology Architecture, Opportunities and Solutions, Migration Planning, Implementation Governance, and Architecture Change Management. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
EA is typically used by companies to produce a blueprint of the future state and a road map for getting there. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
A road map is used to guide an organization with planning and maintaining business goals over time through technology. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
ArchDev is an example of an Accelerated Architecture-Driven Digital Transformation process, which helps companies proactively embed stakeholder interests and sustainability into the companyâs digital growth. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Agile EA Management (AEAM) is a methodology used for software development and project management. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
An enterprise architecture blueprint is a visualization of the architecture at the conceptual, logical, and physical level of an enterprise, showing concepts, their elements, as well as the components that implement the elements and their interrelationships. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
HCC studies the design, development, and deployment of mixed-initiative human-computer systems. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
HCC/HCI is a subfield within computer science concerned with the study of the interaction between people and computers. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Microservices is an approach to building a software solution as a set of small services that may be deployed locally or on the cloud. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Solution architecture management is managing, designing, and describing the solution engineering in relation to specific business problems. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
The software process can be defined as a collection of patterns that define a set of activities, actions, and tasks required to develop computer software. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Software engineering process patterns establish collaborative communication between customers and software engineers to guarantee a successful completion of task patterns within the project requirements and the project scope. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Subsystems are sets of collaborating components performing a given task included in software systems and it is considered a separate entity within a software architecture. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
At a programming language level, components may be represented as modules, classes, objects, or as a set of related functions. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
The requirements model describes the problem set, establishes the context, and identifies the system of forces that hold sway. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Design patterns are a representation of the previous test solutions in relation to specific problems, which are useful for solving future problems. | https://openstax.org/books/introduction-computer-science/pages/10-summary |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.