What is involved in Domain-Driven Design
Find out what the related areas are that Domain-Driven Design connects with, associates with, correlates with or affects, and which require thought, deliberation, analysis, review and discussion. This unique checklist stands out in a sense that it is not per-se designed to give answers, but to engage the reader and lay out a Domain-Driven Design thinking-frame.
How far is your company on its Domain-Driven Design journey?
Take this short survey to gauge your organization’s progress toward Domain-Driven Design leadership. Learn your strongest and weakest areas, and what you can do now to create a strategy that delivers results.
To address the criteria in this checklist for your organization, extensive selected resources are provided for sources of further research and information.
Start the Checklist
Below you will find a quick checklist designed to help you think about which Domain-Driven Design related domains to cover and 208 essential critical questions to check off in that domain.
The following domains are covered:
Domain-Driven Design, ISO/IEC JTC 1/SC 7, Spiral model, Behavior-driven development, Domain expert, Software maintenance, Java Persistence API, Graphical user interface builder, Rapid application development, Event Sourcing, Model-driven architecture, Domain-Driven Design, Event store, Feature-driven development, Domain-specific multimodeling, Pair Programming, Restful Objects, Plain Old CLR Object, Continuous Integration, Java SE, Incremental build model, Domain model, Software development methodology, Test-driven development, Common layers in an information system logical architecture, Iterative and incremental development, Stand-up meeting, Acceptance test–driven development, Aggregate root, Object-oriented analysis and design, Software project management, Software construction, Requirements analysis, Model-driven development, Plain Old Java Object, Waterfall model, Model-driven engineering, Software prototyping, Domain layer, Team software process, Semantic networks, Microsoft Solutions Framework, Value object, User experience, Programming tool, Agile software development, Infrastructure as Code, Software configuration management, Software deployment, Software documentation, Java EE, IEEE Standards Association, Representational state transfer, Continuous Delivery, Integrated development environment, Cleanroom software engineering, Knowledge representation, Dynamic systems development method, .NET Framework, UML tools:
Domain-Driven Design Critical Criteria:
Concentrate on Domain-Driven Design planning and track iterative Domain-Driven Design results.
– Marketing budgets are tighter, consumers are more skeptical, and social media has changed forever the way we talk about Domain-Driven Design. How do we gain traction?
– What will drive Domain-Driven Design change?
– How would one define Domain-Driven Design leadership?
ISO/IEC JTC 1/SC 7 Critical Criteria:
Brainstorm over ISO/IEC JTC 1/SC 7 outcomes and budget the knowledge transfer for any interested in ISO/IEC JTC 1/SC 7.
– Does Domain-Driven Design analysis isolate the fundamental causes of problems?
– Do we all define Domain-Driven Design in the same way?
– Are there recognized Domain-Driven Design problems?
Spiral model Critical Criteria:
Deliberate over Spiral model tasks and prioritize challenges of Spiral model.
– Does Domain-Driven Design create potential expectations in other areas that need to be recognized and considered?
– Are there any disadvantages to implementing Domain-Driven Design? There might be some that are less obvious?
Behavior-driven development Critical Criteria:
Merge Behavior-driven development quality and don’t overlook the obvious.
– For your Domain-Driven Design project, identify and describe the business environment. is there more than one layer to the business environment?
– What other jobs or tasks affect the performance of the steps in the Domain-Driven Design process?
– What new services of functionality will be implemented next with Domain-Driven Design ?
Domain expert Critical Criteria:
Familiarize yourself with Domain expert engagements and tour deciding if Domain expert progress is made.
– Can we do Domain-Driven Design without complex (expensive) analysis?
– Do Nondomain Experts Enlist the Strategies of Domain Experts?
– What is the depth of the vendors domain expertise?
– Where is the domain expertise?
– Are there Domain-Driven Design Models?
Software maintenance Critical Criteria:
Reason over Software maintenance results and arbitrate Software maintenance techniques that enhance teamwork and productivity.
– What are your current levels and trends in key measures or indicators of Domain-Driven Design product and process performance that are important to and directly serve your customers? how do these results compare with the performance of your competitors and other organizations with similar offerings?
– If the path forward waits until a new generation of devices essentially replaces an old generation of devices which could be somewhere between 5 and 15 years, what does the path forward look like for the legacy devices and their software maintenance?
– What are the record-keeping requirements of Domain-Driven Design activities?
– Which Domain-Driven Design goals are the most important?
Java Persistence API Critical Criteria:
Exchange ideas about Java Persistence API issues and assess and formulate effective operational and Java Persistence API strategies.
– What are the disruptive Domain-Driven Design technologies that enable our organization to radically change our business processes?
– What business benefits will Domain-Driven Design goals deliver if achieved?
– Why is Domain-Driven Design important for you now?
Graphical user interface builder Critical Criteria:
Scan Graphical user interface builder quality and oversee Graphical user interface builder requirements.
– Do we cover the five essential competencies-Communication, Collaboration,Innovation, Adaptability, and Leadership that improve an organizations ability to leverage the new Domain-Driven Design in a volatile global economy?
– Think about the functions involved in your Domain-Driven Design project. what processes flow from these functions?
– Are there Domain-Driven Design problems defined?
Rapid application development Critical Criteria:
Refer to Rapid application development adoptions and explain and analyze the challenges of Rapid application development.
– Rapid application development (rad) techniques have been around for about two decades now and have been used with varying degrees of success. sometimes rad is required for certain projects. but rad can be bad for database design. why?
– Schedule feasibility -can the solution be designed and implemented within an acceptable time?
– Who is responsible for modifying or developing programs to satisfy user requirements?
– Who will be responsible for documenting the Domain-Driven Design requirements in detail?
– Operational feasibility -will the solution fulfill the users requirements?
– Are accountability and ownership for Domain-Driven Design clearly defined?
– Which sdlc results in the highest degree of user participation?
– Technical feasibility -is the solution technically practical?
– What primary problems might a new or enhanced system solve?
– What are the primary advantages of the traditional sdlc?
– Did usability perceptions change during the rad proces?
– Economic feasibility -is the solution cost-effective?
– Who are the potential users of the new application?
– How can you tell when a system is successful ?
– Is the functionality visible through the uis?
– How time-constrained is the project?
– What is important for us?
– Is it applicable?
– When use RAD?
Event Sourcing Critical Criteria:
Frame Event Sourcing governance and perfect Event Sourcing conflict management.
– Who is responsible for ensuring appropriate resources (time, people and money) are allocated to Domain-Driven Design?
– How do mission and objectives affect the Domain-Driven Design processes of our organization?
– How do we Improve Domain-Driven Design service perception, and satisfaction?
Model-driven architecture Critical Criteria:
Check Model-driven architecture tasks and find the ideas you already have.
– Meeting the challenge: are missed Domain-Driven Design opportunities costing us money?
– What are the short and long-term Domain-Driven Design goals?
– Why are Domain-Driven Design skills important?
Domain-Driven Design Critical Criteria:
Study Domain-Driven Design risks and balance specific methods for improving Domain-Driven Design results.
– What vendors make products that address the Domain-Driven Design needs?
– What is the purpose of Domain-Driven Design in relation to the mission?
– How much does Domain-Driven Design help?
Event store Critical Criteria:
Think about Event store governance and research ways can we become the Event store company that would put us out of business.
– How does the organization define, manage, and improve its Domain-Driven Design processes?
Feature-driven development Critical Criteria:
Define Feature-driven development tasks and describe the risks of Feature-driven development sustainability.
– Can Management personnel recognize the monetary benefit of Domain-Driven Design?
Domain-specific multimodeling Critical Criteria:
Paraphrase Domain-specific multimodeling failures and create a map for yourself.
– Think about the kind of project structure that would be appropriate for your Domain-Driven Design project. should it be formal and complex, or can it be less formal and relatively simple?
– Do those selected for the Domain-Driven Design team have a good general understanding of what Domain-Driven Design is all about?
Pair Programming Critical Criteria:
Start Pair Programming management and drive action.
– what is the best design framework for Domain-Driven Design organization now that, in a post industrial-age if the top-down, command and control model is no longer relevant?
Restful Objects Critical Criteria:
Substantiate Restful Objects goals and get out your magnifying glass.
Plain Old CLR Object Critical Criteria:
Audit Plain Old CLR Object engagements and report on developing an effective Plain Old CLR Object strategy.
– How important is Domain-Driven Design to the user organizations mission?
– How can we improve Domain-Driven Design?
Continuous Integration Critical Criteria:
Have a session on Continuous Integration tasks and be persistent.
– At what point will vulnerability assessments be performed once Domain-Driven Design is put into production (e.g., ongoing Risk Management after implementation)?
– What are your key performance measures or indicators and in-process measures for the control and improvement of your Domain-Driven Design processes?
– Does your organization run a Continuous Integration and Continuous Delivery (CI/CD) process?
– Will we use Continuous Integration?
Java SE Critical Criteria:
Rank Java SE decisions and modify and define the unique characteristics of interactive Java SE projects.
– Think of your Domain-Driven Design project. what are the main functions?
– Is Domain-Driven Design Required?
Incremental build model Critical Criteria:
Discuss Incremental build model goals and find the ideas you already have.
– How will we insure seamless interoperability of Domain-Driven Design moving forward?
– How will you measure your Domain-Driven Design effectiveness?
Domain model Critical Criteria:
Accelerate Domain model issues and proactively manage Domain model risks.
– Will Domain-Driven Design deliverables need to be tested and, if so, by whom?
– Does Domain-Driven Design appropriately measure and monitor risk?
– What are current Domain-Driven Design Paradigms?
Software development methodology Critical Criteria:
Shape Software development methodology governance and research ways can we become the Software development methodology company that would put us out of business.
– What are our metrics to use to measure the performance of a team using agile software development methodology?
– Is there a Domain-Driven Design Communication plan covering who needs to get what information when?
– In a project to restructure Domain-Driven Design outcomes, which stakeholders would you involve?
– What is our Domain-Driven Design Strategy?
Test-driven development Critical Criteria:
Grasp Test-driven development goals and achieve a single Test-driven development view and bringing data together.
– Which customers cant participate in our Domain-Driven Design domain because they lack skills, wealth, or convenient access to existing solutions?
– How do we make it meaningful in connecting Domain-Driven Design with what users do day-to-day?
Common layers in an information system logical architecture Critical Criteria:
Review Common layers in an information system logical architecture governance and gather Common layers in an information system logical architecture models .
– Who are the people involved in developing and implementing Domain-Driven Design?
Iterative and incremental development Critical Criteria:
Inquire about Iterative and incremental development risks and work towards be a leading Iterative and incremental development expert.
– In the case of a Domain-Driven Design project, the criteria for the audit derive from implementation objectives. an audit of a Domain-Driven Design project involves assessing whether the recommendations outlined for implementation have been met. in other words, can we track that any Domain-Driven Design project is implemented as planned, and is it working?
– Have all basic functions of Domain-Driven Design been defined?
Stand-up meeting Critical Criteria:
Apply Stand-up meeting governance and correct Stand-up meeting management by competencies.
– Can we add value to the current Domain-Driven Design decision-making process (largely qualitative) by incorporating uncertainty modeling (more quantitative)?
– What prevents me from making the changes I know will make me a more effective Domain-Driven Design leader?
– Is there any existing Domain-Driven Design governance structure?
– Stand-up meeting time and format?
Acceptance test–driven development Critical Criteria:
Define Acceptance test–driven development outcomes and correct Acceptance test–driven development management by competencies.
– What may be the consequences for the performance of an organization if all stakeholders are not consulted regarding Domain-Driven Design?
– What role does communication play in the success or failure of a Domain-Driven Design project?
– How can skill-level changes improve Domain-Driven Design?
Aggregate root Critical Criteria:
Mine Aggregate root governance and reinforce and communicate particularly sensitive Aggregate root decisions.
– Do several people in different organizational units assist with the Domain-Driven Design process?
Object-oriented analysis and design Critical Criteria:
Recall Object-oriented analysis and design goals and forecast involvement of future Object-oriented analysis and design projects in development.
– How can the value of Domain-Driven Design be defined?
– Is the scope of Domain-Driven Design defined?
Software project management Critical Criteria:
Drive Software project management adoptions and change contexts.
– Is the Domain-Driven Design organization completing tasks effectively and efficiently?
Software construction Critical Criteria:
X-ray Software construction quality and clarify ways to gain access to competitive Software construction services.
– What are the success criteria that will indicate that Domain-Driven Design objectives have been met and the benefits delivered?
Requirements analysis Critical Criteria:
Mix Requirements analysis management and explore and align the progress in Requirements analysis.
– How can we incorporate support to ensure safe and effective use of Domain-Driven Design into the services that we provide?
– What are the barriers to increased Domain-Driven Design production?
– Are we Assessing Domain-Driven Design and Risk?
Model-driven development Critical Criteria:
Mix Model-driven development tasks and spearhead techniques for implementing Model-driven development.
– To what extent does management recognize Domain-Driven Design as a tool to increase the results?
Plain Old Java Object Critical Criteria:
Analyze Plain Old Java Object tasks and sort Plain Old Java Object activities.
– What are the Essentials of Internal Domain-Driven Design Management?
– What about Domain-Driven Design Analysis of results?
Waterfall model Critical Criteria:
Study Waterfall model planning and know what your objective is.
– How can you negotiate Domain-Driven Design successfully with a stubborn boss, an irate client, or a deceitful coworker?
– What knowledge, skills and characteristics mark a good Domain-Driven Design project manager?
Model-driven engineering Critical Criteria:
Map Model-driven engineering tasks and visualize why should people listen to you regarding Model-driven engineering.
– Are there any easy-to-implement alternatives to Domain-Driven Design? Sometimes other solutions are available that do not require the cost implications of a full-blown project?
– Do we monitor the Domain-Driven Design decisions made and fine tune them as they evolve?
Software prototyping Critical Criteria:
Understand Software prototyping quality and suggest using storytelling to create more compelling Software prototyping projects.
– Do the Domain-Driven Design decisions we make today help people and the planet tomorrow?
– Does our organization need more Domain-Driven Design education?
Domain layer Critical Criteria:
Map Domain layer results and figure out ways to motivate other Domain layer users.
– What are our needs in relation to Domain-Driven Design skills, labor, equipment, and markets?
– What are the business goals Domain-Driven Design is aiming to achieve?
– What are internal and external Domain-Driven Design relations?
Team software process Critical Criteria:
Grasp Team software process tasks and handle a jump-start course to Team software process.
– Among the Domain-Driven Design product and service cost to be estimated, which is considered hardest to estimate?
– Is Supporting Domain-Driven Design documentation required?
Semantic networks Critical Criteria:
Infer Semantic networks projects and spearhead techniques for implementing Semantic networks.
– Are assumptions made in Domain-Driven Design stated explicitly?
Microsoft Solutions Framework Critical Criteria:
Review Microsoft Solutions Framework strategies and reduce Microsoft Solutions Framework costs.
– Who needs to know about Domain-Driven Design ?
– Do we have past Domain-Driven Design Successes?
Value object Critical Criteria:
Consolidate Value object results and spearhead techniques for implementing Value object.
– Record-keeping requirements flow from the records needed as inputs, outputs, controls and for transformation of a Domain-Driven Design process. ask yourself: are the records needed as inputs to the Domain-Driven Design process available?
– What threat is Domain-Driven Design addressing?
User experience Critical Criteria:
Concentrate on User experience engagements and change contexts.
– What are your results for key measures or indicators of the accomplishment of your Domain-Driven Design strategy and action plans, including building and strengthening core competencies?
– What do you think the world of enterprise software delivery will look like in ten to fifteen years (take into account practices, technology, and user experience)?
– How can I avoid duplication of identity, attributes, and credentials and provide a single sign-on user experience for my users?
– Where does User Experience come from, what does it add to the software development process and what methods are available?
– What is the difference between information architecture and user experience design?
– What are the potential impacts to user experience by using a cloud-based service?
– What are the problems when integrating Agile Development and User Experience?
– Agile-User Experience Design: With or Without a Usability Expert in the Team?
– What is the difference between customer experience and user experience?
– What are the best-practices for creating a good User Experience?
– What does User Experience do?
– What is User Experience?
Programming tool Critical Criteria:
Systematize Programming tool governance and suggest using storytelling to create more compelling Programming tool projects.
Agile software development Critical Criteria:
Refer to Agile software development risks and correct better engagement with Agile software development results.
– When you are identifying the potential technical strategy(s) you have several process factors that you should address. As with initial scoping how much detail you go into when documenting the architecture, the views that you create, and your approach to modeling are important considerations. Furthermore, will you be considering one or more candidate architectures and what is your overall delivery strategy?
– How do you take a methodology, like agile development, that basically evolved in small groups and then scale it up so that it works on projects with hundreds of developers and thousands of users?
– Does the organization have a distinct quality program that support continuous process improvement?
– Are there cultural or organizational issues that may affect the system development?
– How do you know when the software will be finished if theres no up-front plan?
– Which is really software best practice to us, CMM or agile development?
– To what level of detail will you capture the requirements, if at all?
– What are the a best practices for Agile SCRUM Product Management?
– Who will provide the final approval of Domain-Driven Design deliverables?
– Will the broader project community be populated appropriately?
– What is your favorite project managment interview question?
– So what do your developers do differently in agile?
– How could a more enhanced framework be developed?
– How do disciplined agile teams work at scale?
– Will the team be populated by stakeholders?
– What are you planning to complete today?
– How do engineers feel about it?
– What Is Extreme Programming?
– Why Agile, and Why Now?
Infrastructure as Code Critical Criteria:
Reorganize Infrastructure as Code visions and track iterative Infrastructure as Code results.
– What are our Domain-Driven Design Processes?
Software configuration management Critical Criteria:
Align Software configuration management risks and devote time assessing Software configuration management and its risk.
– What are some of the software Configuration Management tools?
– What is our formula for success in Domain-Driven Design ?
– Definition: what is software Configuration Management?
– Motivation: why software Configuration Management?
– Why software Configuration Management ?
Software deployment Critical Criteria:
X-ray Software deployment strategies and integrate design thinking in Software deployment innovation.
Software documentation Critical Criteria:
Facilitate Software documentation management and check on ways to get started with Software documentation.
– What sources do you use to gather information for a Domain-Driven Design study?
Java EE Critical Criteria:
Dissect Java EE failures and modify and define the unique characteristics of interactive Java EE projects.
IEEE Standards Association Critical Criteria:
Co-operate on IEEE Standards Association strategies and stake your claim.
– Which individuals, teams or departments will be involved in Domain-Driven Design?
Representational state transfer Critical Criteria:
Adapt Representational state transfer outcomes and oversee implementation of Representational state transfer.
– Will new equipment/products be required to facilitate Domain-Driven Design delivery for example is new software needed?
– Have you identified your Domain-Driven Design key performance indicators?
Continuous Delivery Critical Criteria:
Consult on Continuous Delivery outcomes and probe the present value of growth of Continuous Delivery.
– A competitive edge, excellent. Focus on continuous delivery. Move on to continuous deployment because that is going to provide your business value. But look at your individual business. Look at your environment and say is that what gives us the competitive edge?
– Does your organization hope to achieve continuous delivery?
– How do we go about Securing Domain-Driven Design?
Integrated development environment Critical Criteria:
Bootstrap Integrated development environment quality and probe the present value of growth of Integrated development environment.
– What is the source of the strategies for Domain-Driven Design strengthening and reform?
Cleanroom software engineering Critical Criteria:
Set goals for Cleanroom software engineering risks and question.
– How likely is the current Domain-Driven Design plan to come in on schedule or on budget?
– What are the long-term Domain-Driven Design goals?
– How do we maintain Domain-Driven Designs Integrity?
Knowledge representation Critical Criteria:
Confer re Knowledge representation leadership and clarify ways to gain access to competitive Knowledge representation services.
– Who will be responsible for making the decisions to include or exclude requested changes once Domain-Driven Design is underway?
– What are your most important goals for the strategic Domain-Driven Design objectives?
Dynamic systems development method Critical Criteria:
Tête-à-tête about Dynamic systems development method management and learn.
– When a Domain-Driven Design manager recognizes a problem, what options are available?
.NET Framework Critical Criteria:
Design .NET Framework leadership and maintain .NET Framework for success.
– Risk factors: what are the characteristics of Domain-Driven Design that make it risky?
UML tools Critical Criteria:
Value UML tools tasks and acquire concise UML tools education.
This quick readiness checklist is a selected resource to help you move forward. Learn more about how to achieve comprehensive insights with the Domain-Driven Design Self Assessment:
Author: Gerard Blokdijk
CEO at The Art of Service | http://theartofservice.com
Gerard is the CEO at The Art of Service. He has been providing information technology insights, talks, tools and products to organizations in a wide range of industries for over 25 years. Gerard is a widely recognized and respected information expert. Gerard founded The Art of Service consulting business in 2000. Gerard has authored numerous published books to date.
To address the criteria in this checklist, these selected resources are provided for sources of further research and information:
ISO/IEC JTC 1/SC 7 External links:
ISO/IEC JTC 1/SC 7 – History (kb) – startupcto.io
US TAG to ISO/IEC JTC 1/SC 7, Software and Systems …
[PDF]ISO/IEC JTC 1/SC 7 N XXXX 2 Date: 2007-06-15 – IEEE-SA
Spiral model External links:
Boehm’s Spiral Model Flashcards | Quizlet
SDLC Spiral Model – Tutorials Point
The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software [Barry Boehm, Jo Ann Lane, …
Behavior-driven development External links:
Behavior-Driven Development: The Origins – DZone Agile
Software maintenance External links:
Citrix Software Maintenance Support Program – Citrix
Java Persistence API External links:
Java Persistence API (JPA) 2.1 | Pluralsight
Java Persistence API
http://The Java Persistence API (JPA) is a Java specification for accessing, persisting, and managing data between Java objects / classes and a relational database. JPA was defined as part of the EJB 3.0 specification as a replacement for the EJB 2 CMP Entity Beans specification.
Graphical user interface builder External links:
Graphical user interface builder – YouTube
A graphical user interface builder for Tk – dl.acm.org
Rapid application development External links:
Pega 7 Platform: Rapid Application Development | Pega
Best Rapid Application Development (RAD) Software in …
What’s a rapid application development model? – Quora
Model-driven architecture External links:
Model-Driven Architecture (MDA) – Gartner IT Glossary
Event store External links:
Overview – Event Store
Getting Started – Event Store
Feature-driven development External links:
An Introduction to Feature-Driven Development – DZone …
Domain-specific multimodeling External links:
Domain-specific multimodeling – WOW.com
Domain-specific multimodeling – SEOmastering.com
Restful Objects External links:
Restful Objects · GitHub
Plain Old CLR Object External links:
POCO – Plain Old CLR Object | AcronymFinder
Plain Old CLR Object – YouTube
Plain Old CLR Object | dotnethelpers
Continuous Integration External links:
Continuous Integration Using Salesforce DX – Trailhead
Learning Continuous Integration with Jenkins PDF Free Download, Reviews, Read Online, ISBN: B01BFD2Z2G, By Nikhil Pathania
Java SE External links:
Java SE Development Kit (JDK) Download – softpedia.com
http://www.softpedia.com › … › Debuggers/Decompilers/Disassemblers
Java SE 8 Certification Bundle – GogoTraining | Groupon
Incremental build model External links:
Incremental Build model | COMPLEX TESTER
Incremental Build Model – YouTube
Incremental Build Model – YouTube
Domain model External links:
Social Tenure Domain Model Philippines – Home | Facebook
Multi-Scale Multi-Domain Model | Transportation …
Software development methodology External links:
Best software development methodology for sole programmer
CIS 610 | Software Development Methodology – CSU Online
Test-driven development External links:
Test-Driven Development with Python | TechLife …
Iterative and incremental development External links:
Iterative and incremental development – YouTube
[PDF]Iterative and Incremental Development (IID)
Aggregate root External links:
Singleton aggregate root? – Google Groups
Using Aggregate Root Cause Analysis to Reduce Falls …
design patterns – What’s an Aggregate Root? – Stack Overflow
Software project management External links:
Full-stack Software Project Management Tools – Unfuddle
Requirements analysis External links:
[PDF]VIII. Requirements Analysis – University of Toronto
Business Requirements Analysis – Project Management …
Wilderness.net – Minimum Requirements Analysis
Model-driven development External links:
Model-Driven Development of .NET Enterprise Applications
Plain Old Java Object External links:
POJO (Plain Old Java Object) | Monologue
Plain Old Java Object – YouTube
plain old java object Archives – SD Times
Waterfall model External links:
SDLC – Waterfall Model – tutorialspoint.com
Waterfall model documentation – Stack Overflow
Prototype and Waterfall Model Flashcards | Quizlet
Model-driven engineering External links:
PlugBee | Model-Driven Engineering
[PDF]System Integration using Model-Driven Engineering
Software prototyping External links:
Software Prototyping Services | Bitsapphire
[PDF]Methods for Software Prototyping
Software Prototyping | Rapid Prototyping | AgileThought
Team software process External links:
[PDF]Team Software Process (TSP) – Georgia Tech STAR …
[PDF]Team Software Process (TSP) Coach Mentoring …
Team Software Process | Overview
Semantic networks External links:
[PDF]Auditory semantic networks for words and natural …
Semantic Networks – Duke University
Semantic Networks Flashcards | Quizlet
Microsoft Solutions Framework External links:
Download Microsoft Solutions Framework Core …
Microsoft Solutions Framework Team Model and Team System
Download Microsoft Solutions Framework Version 3 …
Value object External links:
Value Objects Explained with Ruby — SitePoint
Value Objects in Java & Python | Steve Wedig’s Notes
User experience External links:
Google User Experience Research
User Experience | UX Design Tools | Optimal Workshop
User Experience Professionals Association
Programming tool External links:
MAX WITH OBDII Diagnostic & Programming Tool | The Wheel Group
XKLOADER2 – 2nd Gen XPRESSKIT Computer Programming tool
ATEQ VT36 TPMS Programming Tool – Tire Rack
Agile software development External links:
Introducing Agile Software Development
Infrastructure as Code External links:
‘Infrastructure as Code’ in Chicago (Chicago, IL) | Meetup
Implementing Infrastructure as Code | ThoughtWorks …
Software configuration management External links:
[PDF]Software Configuration Management A Clear Case …
Software configuration management
http://In software engineering, software configuration management (SCM or S/W CM) is the task of tracking and controlling changes in the software, part of the larger cross-disciplinary field of configuration management. SCM practices include revision control and the establishment of baselines. If something goes wrong, SCM can determine what was changed and who changed it.
[PDF]Software Configuration Management
Software deployment External links:
[PDF]Automating Software Deployment – New York University
Software Deployment Jobs, Employment | Indeed.com
Software documentation External links:
Label Print MIS Software Documentation | Label Traxx
Progress® Software Documentation
Software Documentation – FIREHOUSE Software®
Java EE External links:
The Java EE 5 Tutorial – Oracle
IEEE Standards Association External links:
IEEE Standards Association – Documents
IEEE Standards Association – Official Site
IEEE Standards Association – Sign In
Representational state transfer External links:
Representational State Transfer (REST) – Service Architecture
Representational State Transfer (REST) – reddit
Continuous Delivery External links:
What is Continuous Delivery? – Continuous Delivery
Continuous Delivery (eBook, 2014) [WorldCat.org]
Continuous Delivery – CA Technologies
Integrated development environment External links:
Integrated Development Environment (IDE) – Progress …
Cleanroom software engineering External links:
Cleanroom Software Engineering – Critiques
[DOC]Cleanroom Software Engineering
[PDF]Cleanroom Software Engineering – Georgia Tech …
Knowledge representation External links:
Knowledge Representation and Reasoning – …
Semantic Knowledge Representation – SemRep
Dynamic systems development method External links:
Dynamic Systems Development Method – YouTube
Dynamic Systems Development Method (DSDM) – Prezi
Dynamic Systems Development Method Archives – SPC …
.NET Framework External links:
Microsoft .NET Framework 4.7 coming to WSUS – WSUS …
Download Microsoft .NET Framework 3.5 Service pack 1 …