SDLC Artifact Validation System for Standard Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional SDLC documentation practices lack standardization and consistency, leading to inefficiencies in processing time and resource consumption due to missing sections, out-of-date artifacts, and the need for multiple tools and versions, causing difficulties in validation and compliance with established standards.

Innovation Solution

A computer-implemented system and method for creating and validating SDLC digital artifacts, which includes a processor configured to receive and validate templates created on a user interface, map properties, associate metadata and approvers, and transform artifacts into standard-compliant forms, utilizing a network of servers for approval and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional SDLC documentation practices are used, then flexibility in document creation is maintained, but standardization and consistency are lost leading to validation issues and compliance problems

Engineering Contradiction:
Improveflexibility in document creationVSAvoidstandardization and consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The system changes the parameters of document templates by enforcing standardized structures, required sections, and formatting rules. Templates define specific parameters that documents must satisfy, transforming flexible document creation into a controlled process that maintains both adaptability and standardization.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent introduces templates as an intermediary between users and the final documentation. Templates act as a mediator that guides document creation, ensuring standardization while allowing flexibility within the template-defined framework. The template validation mechanism serves as an intermediary check to enforce consistency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple tools and design documents are required for artifact validation, then comprehensive validation coverage is achieved, but processing time and resource consumption increase

Engineering Contradiction:
Improvevalidation coverageVSAvoidprocessing time and resource consumption
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple validation functions into a single integrated template validation process. The system combines syntax validation, semantic validation, compliance checking, and approval workflow validation into one unified mechanism, reducing the need for multiple separate tools while maintaining comprehensive validation coverage.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The template validation system serves multiple functions simultaneously: it validates document structure, checks compliance with standards, manages approval workflows, and ensures consistency across artifacts. This multi-functional approach replaces multiple specialized tools with a single universal validation mechanism.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If design documents are distributed widely through emails and communications, then accessibility is improved, but version control and location tracking become difficult

Engineering Contradiction:
Improvedocument accessibilityVSAvoidversion control and location tracking
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms through automated notifications and status tracking. When documents are updated or approved, the system automatically notifies relevant stakeholders and updates the approval status, providing continuous feedback on document versions and locations without requiring manual tracking.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent uses digital copying and distribution of approved templates through the system, ensuring that all users access the same validated version. The system maintains master copies of templates and automatically distributes updated versions, eliminating the need for manual email distribution while preserving version control.

Inventive Principle:
Principle #26Copying

4Reliability

If manual investigation and resolution of artifact issues is performed, then thorough problem solving is achieved, but time and human resources are consumed

Engineering Contradiction:
Improveproblem resolution thoroughnessVSAvoidtime and human resources for issue resolution
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service validation by automatically checking documents against template requirements and compliance standards. The validation process occurs automatically without requiring manual investigation, with the system itself identifying and reporting issues, thereby reducing human resource consumption while maintaining thorough problem solving.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary validation actions by checking documents against templates before formal approval is required. This preliminary validation identifies issues early in the process, preventing the need for extensive manual investigation later and enabling faster resolution of problems.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10922075B2System and method for creating and validating software development life cycle (SDLC) digital artifacts
Publication Date: 2021.02.16 MORGAN STANLEY SERVICES GROUP INC
  • US10922075B2 patent drawing
  • US10922075B2 patent drawing
  • US10922075B2 patent drawing

AI summary

Systems and methods for creating and validating software development life cycle (“SDLC”) digital artifacts are disclosed. In an embodiment, a computer-implemented system includes a processor that is configured to determine whether a template of an SDLC artifact is valid, and in response to a determination that the template of the SDLC artifact is valid, to map one or more properties to the template. In an embodiment, the processor is configured to associate software asset metadata and one or more approvers of the SDLC artifact, and to transform the SDLC artifact into a standard-compliant SDLC artifact.