Patent application number | Description | Published |
20080255693 | Software Factory Readiness Review - A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: determining if an infrastructure for a software factory has been procured; determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed; determining if a workflow event model for an assembly line in the software factory has been configured; determining if workload in the assembly line has been balanced; determining if communication channels between the software factory and a customer's computer system have been defined and cleared for data transmission; and in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory. | 10-16-2008 |
20080255696 | Software Factory Health Monitoring - A method, system, and computer-readable medium for maintaining a health of a software factory that creates custom software in a standardized manner is presented. In a preferred embodiment, the method includes the steps of: defining work packets to perform sub-functions of a custom software; tracking a transmission of the work packets to an assembly line in a software factory; monitoring any retrieval of software artifacts that are used to create the work packets; monitoring any on-going changes of work activities that are contained in the work packets; determining if execution of the work packets conforms to governance guidelines for the software factory; monitoring the software factory to ensure that the work packets comply with an architecture of the software factory; tracking quality metrics for an execution of the work packets in an assembly line in the software factory; and transmitting all tracked and monitored information described above to a dashboard. | 10-16-2008 |
20080256390 | Project Induction in a Software Factory - A computer-implemented method, system, and computer-readable medium for inducting a software project into a software factory is presented, wherein an induction process identifies what processes and sub-processes are needed to create the software factory, and wherein the induction process identifies potential risks to the software factory. In a preferred embodiment, the computer-implemented method comprises the steps of: submitting a factory project proposal to a service definition process; creating a service definition template from a compilation of selected checklists; scoring and classifying the service definition template to determine if the candidate project may be executed in the software factory; in response to the service definition template scoring above a pre-determined acceptable score, transmitting the factory project proposal to a service induction process; and in response to the candidate project passing a final review process, transmitting the candidate project to the software factory for execution. | 10-16-2008 |
20080256505 | Rapid On-Boarding of a Software Factory - A method, system, and computer-readable medium for rapid on-boarding of a software factory are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: identifying choke-points in a first software project; creating a checklist of identifying factors that caused the choke-points that were identified in the first software project; receiving a new software project at a software factory, wherein the new software project is in a same software category as the first software project; presenting the checklist for the first software project; receiving new answers to the checklist; determining if the software factory is ready to handle the new software project based on the new answers to the checklist; and in response to determining that the software factory is ready to handle the new software project, configuring the software factory in a same configuration as that previously used by the first software project. | 10-16-2008 |
20080256506 | Assembling Work Packets Within a Software Factory - A method, system, and computer-readable medium for assembling work packets within a software factory are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: collecting a plurality of software artifacts that have been archived during an assembly of previous work packets; collecting a plurality of metrics that have been utilized during the assembly of previous work packets; defining a template for a new work packet, wherein the template for the new work packet is created by a packet definition process that defines attributes that are needed in the new work packet; selecting requisite software artifacts from the plurality of software artifacts; selecting requisite metrics from the plurality of metrics; and sending the template, requisite software artifacts and requisite metrics to a packet assembly process, wherein the packet assembly process assembles the requisite software artifacts to create the new work packet. | 10-16-2008 |
20080256507 | Life Cycle of a Work Packet in a Software Factory - A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software. | 10-16-2008 |
20080256516 | Software Factory - A method, system and computer-readable medium for creating software in a standardized manner are presented. The method includes the steps of: receiving, at a software factory, a description of software needs from a customer; creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs; inducting the project proposal into the software factory, wherein inducting the project proposal initially evaluates the project proposal's compatibility with a capacity of the software factory; parsing the project proposal into major functional areas; retrieving work packets that are appropriate for the project proposal, wherein the work packets are pre-stored, reusable, self-contained, discrete units of software code; assembling the work packets into a deliverable software; testing the deliverable software; and delivering the deliverable software to the customer. | 10-16-2008 |
20080256529 | Work Packet Forecasting in a Software Factory - A method, system, and computer-readable medium for predicatively selecting which work packets will be needed by a software factory to create a deliverable custom software are presented. In a preferred embodiment, the computer-implemented method includes: presenting an initial checklist that consists of a series of question groups; receiving answers to the initial checklist; in response to determining that received answers to the initial checklist indicate that a new series of questions is required to predict which work packets will be needed to create the deliverable custom software, dynamically generating a new checklist; evaluating leading indicators for the received answers; based on relevancy of answers and the leading indicators, eliminating irrelevant questions from the new checklist; and based on answers to remaining relevant questions, determining if a particular work packet will be needed to create the deliverable custom software in the software factory. | 10-16-2008 |
20090019427 | Method and Apparatus for Providing Requirement Driven Static Analysis of Test Coverage for Web-Based, Distributed Processes - A method (which can be computer implemented) for analyzing test coverage of distributed processes includes the steps of identifying at least one of the processes that is invoked by a test case, mapping at least a portion of the test case to a plurality of specific test paths in the at least one of the processes, and identifying given ones of the test paths as possibly relevant in at least one of the processes, if the test paths are not infeasible. | 01-15-2009 |
20090019428 | Method for Analyzing Transaction Traces to Enable Process Testing - Techniques are provided for analyzing testing coverage of one or more software modules to provide process coverage statistics. The techniques include obtaining one or more coverage measures from a test specification document, performing a trace on each of the one or more coverage measures during a test, analyzing each trace to generate a run-time service choreography model for a process, wherein the model includes each of one or more service choreography patterns occurring in the process, and using the model to provide statistical data on test coverage according to a process definition. | 01-15-2009 |
20090043622 | Waste Determinants Identification and Elimination Process Model Within a Software Factory Operating Environment - Within the context of a software factory, process sensors detect time consuming activities that extend beyond an estimated predetermined completion timeline for a project. These process sensors also detect wait states that are caused by processes and activities of tasks that are not critical to completing the project. A process analysis is used to determine if defined added value processes and activities identified in a value stream analysis are interdependent to a critical path for executing the project. If the defined added value processes and activities identified in the value stream analysis are determined to not be interdependent to the critical path for executing the project, then a determination is made that performance of the defined added value processes and activities identified in the value stream analysis is wasteful and such processes and activities are eliminated from the process. | 02-12-2009 |
20090043631 | Dynamic Routing and Load Balancing Packet Distribution with a Software Factory - A system decision engine enables a software factory to effectively handle intelligent load balancing and distribution to workers on a software assembly line through the use of pre-configured rules. The pre-configured rules are based on a projected availability of workers based on past traffic analysis of work packets being sent to particular workers on the software assembly line. | 02-12-2009 |
20090044168 | METHOD, SYSTEM AND PROGRAM PRODUCT FOR GENERATING REQUIREMENT RELATIONSHIPS FOR DESIGNING A SOLUTION - A method, system and program product for generating requirement patterns for designing a domain based solution. The method includes inputting, into a pattern tool, requirements for designing a solution based on a defined domain context, the requirements including attributes and specifications. The method further includes determining relationship requirement patterns using relationship mappings formed by mapping specifications to an attribute and defining affinities for the relationship mappings formed. Further, the method includes creating domain requirement patterns using the domain context defined, the relationship mappings formed and the affinities defined and generating domain trait requirement patterns using the domain requirement patterns created and using selected values assigned to the specifications mapped, such that the domain trait requirement patterns generated dictate a domain specific design for the solution. Furthermore, the method includes storing attributes, specifications, relationship requirement patterns, domain requirement patterns and domain trait requirement patterns in a repository. | 02-12-2009 |
20090055795 | System to Monitor and Maintain Balance of Factory Quality Attributes Within a Software Factory Operating Environment - A System to Maintain Balance of Factory Quality Attributes with Software Factory Operating Environment provides the means to determine if a deliverable will meet the needs of a client's project. The process includes the identification and measurement of different parameters of a software factory, including specified architectural features, and compares these parameters with the factory's strategic artifacts and client's critical project needs to qualify attributes within the software factory environment. This process provides a means to monitor and maintain an optimal balance of desirable quality attributes. Thus, quality attributes are analyzed before design time and before delivery of a software product, such that an analysis can be performed before any considerable amount of time and efforts have been spent on a project. | 02-26-2009 |
20090064322 | Security Process Model for Tasks Within a Software Factory - Security for a software factory is provided by detecting a request by a user to utilize the software factory. Upon being authenticated, the user is granted permission to access specific areas of the software factory. A log is created of locations in software factory that have been accessed by the user. This log is then utilized in an audit that describes how effective the software factory is in creating deliverable software. | 03-05-2009 |
20090319832 | METHOD AND APPARATUS OF EFFECTIVE FUNCTIONAL TEST DATA GENERATION FOR WEB SERVICE TESTING - A method, system and apparatus for generating test data for web services testing load a selected file describing one or more web services operations into memory, select an operation specified in said loaded file, and identify one or more fields used in said operation. The one or more fields are customized and the customization is validated. Generation rules are configured and one or more variations of the fields are generated. | 12-24-2009 |
20130014079 | SOFTWARE FACTORY READINESS REVIEW - A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: determining if an infrastructure for a software factory has been procured; determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed; determining if a workflow event model for an assembly line in the software factory has been configured; determining if workload in the assembly line has been balanced; determining if communication channels between the software factory and a customer's computer system have been defined and cleared for data transmission; and in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory. | 01-10-2013 |