Listing 1 - 10 of 18 | << page >> |
Sort by
|
Choose an application
This book introduces a practical methodology for architecture design that any professional software engineer can use, provides structured methods supported by reusable chunks of design knowledge, and includes rich case studies that demonstrate how to use the methods. Using realistic examples, you’ll master the powerful new version of the proven Attribute-Driven Design (ADD) 3.0 method and will learn how to use it to address key drivers, including quality attributes, such as modifiability, usability, and availability, along with functional requirements and architectural concerns.Drawing on their extensive experience, Humberto Cervantes and Rick Kazman guide you through crafting practical designs that support the full software life cycle, from requirements to maintenance and evolution. You’ll learn how to successfully integrate design in your organizational context, and how to design systems that will be built with agile methods.
Choose an application
Programming --- Computer architecture. Operating systems --- Software architecture --- System Design --- Computer architecture --- Computer software --- System design --- 681.3*D0 --- 005.1 --- Design, System --- Systems design --- Electronic data processing --- System analysis --- Software, Computer --- Computer systems --- Architecture, Computer --- Computerwetenschap--?*D0 --- Software architecture. --- System design. --- Architecture, Software --- Computer software architecture --- Architecture --- Design
Choose an application
Programming --- Computer software --- Computer architecture --- Evaluation --- 681.3*D211 --- -Computer architecture --- -Architecture, Computer --- Software, Computer --- Computer systems --- Software architectures: data abstractio, domain-specific architectures, information hiding, languages (e.g. description, interconnection, definition), patterns (e.g. client/server, pipeline, blackboard) --- -Software architectures: data abstractio, domain-specific architectures, information hiding, languages (e.g. description, interconnection, definition), patterns (e.g. client/server, pipeline, blackboard) --- Architecture, Computer --- Computer software - Evaluation --- Computer architecture - Evaluation
Choose an application
In the short space of about a decade, Commercial-Off-the-Shelf (COTS) software has evolved through being a relatively minor aspect of software development; a t- management-endorsedsilverbulletsolutionforsoftwaredevelopment;adisruptivete- nology requiring people and organizations to extensively rethink their approaches to software development; to an increasingly well-understood software phenomenon for which effective solutions are being developed. Part of this understanding has been to recognize that different COTS application sectors can be at different stages of this evolution. Some sectors are just beginning to become COTS-intensive. Some have evolved COTS solutions that are very well matched to their problem domain. Others, including most large-scale applications, still involve their developers in rethinking how to adapt their traditional software architectures, processes, management practices, and personnel skills to accommodate economically attractive but complex combinations of powerful but incompletely compatible and independently evolving COTS products. The series of International Conferences on COTS-Based Software Systems (ICCBSS) has been established as a continuing forum for bringing together CBSS developers, s- pliers, and researchers to summarize and discuss progress toward understanding and resolving CBSS problems. This year’s conference theme, “Matching Solutions to P- blems,"re?ectsthisobjective.Wehavebeenfortunatetohavethreeoutstandingkeynote speakers, David Carr, Tricia Oberndorf, and Douglas Schmidt, who have contributed signi?cantly both in analyzing CBSS problems and developing better CBSS solutions. The contributed papers and summaries of workshops, panels, and tutorials in these ProceedingsgiveagoodunderstandingofthenatureanddirectionsofevolutionofCBSS problems and solutions.As has been my experience with previous ICCBSS Proceedings volumes, I believe that you will ?nd lasting value in the content of the Proceedings.
Computer science. --- Software engineering. --- Information systems. --- Information Systems. --- Computer Science. --- Management of Computing and Information Systems. --- Software Engineering. --- Computer Appl. in Administrative Data Processing. --- Computer software --- Software engineering --- Engineering & Applied Sciences --- Computer Science --- Application software. --- Management information systems. --- Software Engineering/Programming and Operating Systems. --- Computer software engineering --- Engineering --- Application computer programs --- Application computer software --- Applications software --- Apps (Computer software) --- Informatics --- Science --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Management --- Communication systems --- Electronic data processing --- Information technology --- IT Operations. --- Computer Application in Administrative Data Processing. --- Management.
Choose an application
681.3*D29 --- 681.3*D211 --- 681.3*D2 --- 681.3*D2 Software engineering: protection mechanisms standards--See also {681.3*K63} {681.3*K51} --- Software engineering: protection mechanisms standards--See also {681.3*K63} {681.3*K51} --- 681.3*D29 Management: copyrights cost estimation life cycle productivity programming teams software configuration management software quality assurance SQA (Software engineering)--See also {681.3*K63} {681.3*K64} --- Management: copyrights cost estimation life cycle productivity programming teams software configuration management software quality assurance SQA (Software engineering)--See also {681.3*K63} {681.3*K64} --- Software architectures: data abstractio, domain-specific architectures, information hiding, languages (e.g. description, interconnection, definition), patterns (e.g. client/server, pipeline, blackboard) --- 681.3*D2 Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Software architecture. --- System design. --- Computer architecture --- Computer software --- System design --- Design, System --- Systems design --- Electronic data processing --- System analysis --- Software, Computer --- Computer systems --- Architecture, Computer --- 681.3*D29 Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64} --- Management: copyrights; cost estimation; life cycle; productivity; programming teams; software configuration management; software quality assurance; SQA (Software engineering)--See also {681.3*K63}; {681.3*K64}
Choose an application
Software architecture --- System design --- 681.3*D2 --- 681.3*K51 --- 681.3*K63 --- 005.1 --- 681.3*K63 Software management: software development software selection software maintenance --- Software management: software development software selection software maintenance --- 681.3*K51 Software protection: copyrights patents proprietary rights trade secrets (Legal aspects of computing) --- Software protection: copyrights patents proprietary rights trade secrets (Legal aspects of computing) --- Design, System --- Systems design --- Electronic data processing --- System analysis --- Architecture, Software --- Computer software --- Computer software architecture --- 681.3*D2 Software engineering: protection mechanisms standards--See also {681.3*K63} {681.3*K51} --- Software engineering: protection mechanisms standards--See also {681.3*K63} {681.3*K51} --- Architecture --- Design --- 681.3*K63 Software management: software development; software selection; software maintenance --- Software management: software development; software selection; software maintenance --- 681.3*K51 Software protection: copyrights; patents; proprietary rights; trade secrets (Legal aspects of computing) --- Software protection: copyrights; patents; proprietary rights; trade secrets (Legal aspects of computing) --- 681.3*D2 Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- System Design --- Software architecture. --- System design.
Choose an application
Three renowned software architects cover the entire lifecycle, presenting practical guidance, expert methods, and tested models for use in any project, no matter how complex. You'll learn how to use architecture to address accelerating growth in requirements, system size, and abstraction, and to manage emergent quality attributes as systems are dynamically combined in new ways.With insights for utilizing architecture to optimize key quality attributes--including performance, modifiability, security, availability, interoperability, testability, usability, deployability, and more--this guide explains how to manage and refine existing architectures, transform them to solve new problems, and build reusable architectures that become strategic business assets.
Software architecture --- Software engineering --- Computer software engineering --- Engineering --- Architecture, Software --- Computer software --- Computer software architecture --- Architecture --- Design --- 681.3*D2 --- 681.3*D2 Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51} --- Software engineering: protection mechanisms; standards--See also {681.3*K63}; {681.3*K51}
Choose an application
"A look at technical debt in software that focuses on the practical implications of technical debt for the entire software lifecycle"--
Computer software --- Software failures --- Project management. --- Maintainability (Engineering) --- Development --- Quality control. --- Prevention. --- Maintainability of equipment --- Serviceability (Engineering) --- Engineering --- Operations research --- Systems engineering --- Industrial project management --- Management --- Bugs, Software --- Failure of computer software --- Failures, Software --- Software bugs --- Computer system failures --- Debugging in computer science --- Software, Computer --- Computer systems --- Failures --- COMPUTERS / Computer Science --- COMPUTERS / Software Development & Engineering / Systems Analysis & Design --- TECHNOLOGY & ENGINEERING / Reference
Choose an application
Choose an application
Introducing the fundamental concepts and identifying best practices in the field, this textbook explains the role of software architecture in achieving system quality, its importance for a company's business strategy, and the specifics of how software is structured and how its components interact. Technical topics related to the design, specification, and validation of a system are detailed, with particular attention to the relevance of a project's business context. Case studies profiling successful architecture illustrate key points in both the technical and the organizational discussion. The authors are software engineers.
Listing 1 - 10 of 18 | << page >> |
Sort by
|