+

WO2020123993A2 - Systèmes et procédés d'ingénierie et de gestion de produit collaboratives - Google Patents

Systèmes et procédés d'ingénierie et de gestion de produit collaboratives Download PDF

Info

Publication number
WO2020123993A2
WO2020123993A2 PCT/US2019/066310 US2019066310W WO2020123993A2 WO 2020123993 A2 WO2020123993 A2 WO 2020123993A2 US 2019066310 W US2019066310 W US 2019066310W WO 2020123993 A2 WO2020123993 A2 WO 2020123993A2
Authority
WO
WIPO (PCT)
Prior art keywords
platform
product
project
module
resources
Prior art date
Application number
PCT/US2019/066310
Other languages
English (en)
Other versions
WO2020123993A3 (fr
Inventor
Vasavada Vimarsh PRAKASHBHAI
Desai Mehul DILIP
Original Assignee
Peaas, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Peaas, Llc filed Critical Peaas, Llc
Publication of WO2020123993A2 publication Critical patent/WO2020123993A2/fr
Publication of WO2020123993A3 publication Critical patent/WO2020123993A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services

Definitions

  • This application relates to the field of collaborative product engineering and management. More particularly, this application relates to an enterprise platform for delivering product engineering as a service through enabling coordinated development of human resources, product, and intellectual property on behalf of a third party by a host of the platform
  • IP enterprise intellectual property
  • Applicant has identified a need exists for systems that could effectively configure various factors of the product engineering life-cycle to optimize organizational resources while maintaining control over information interchange and enterprise IP.
  • a first aspect provided herein includes a method for delivering software product engineering as a service to a customer by a host organization, comprising: presenting an interface to a user in the host organization to recei ve specifications for a software product; determining resource requirements including competency requirements for building the software product based on the specifications; identifying available resources in the host organization, the available resources having available competencies matching the competency requirements for building the software product; organizing of the identified available resources around a software product engineering life-cycle plan for the software product; providing a set of training and development tools for the identified available resources useful for developing the software product; and delivering the developed software product to the customer.
  • the specifications include: a brief or detailed description of an idea for a new product, a problem addressed by the new product, a scope of work, and details about features of the new product.
  • the delivering of the software product engineering as a service to the customer by the host organization includes communicating with the user for clarifications or details related to the specifications.
  • the method further comprises receiving feedback during the software product engineering life-cycle plan for the software product from the user or the customer and incorporating the feedback to iterate on the software product.
  • the method further comprises: determining a resource shortage including unfilled competencies based on the resource requirements and the available resources; and adding additional resources to the available resources to reduce the resource shortage in time to execute the software product engineering life-cycle plan.
  • the software product engineering life-cycle plan includes project phases selected from the group consisting of: a prototyping and design phase; a development of a web application phase; a parallel development of a native android and an IOS application phase; a testing and quality analysis (QA) phase; and a hosting and a release phase.
  • the software product engineering life-cycle plan has deliverables to be provided at an end of the project phases, wherein the deliverables are selected from the group consisting of: a design document; a prototype; a source code for a web application; a source code for a native android application; a source code for an iOS application; a user manual; technical documentation of the software product; and a deployed application on a production server.
  • the software product engineering life-cycle plan has engineering phases including a concept phase, a design phase, an architecture phase; a development phase; and a hosting phase.
  • the software product engineering life-cycle plan has deliverables to be provided at the end of the engineering phases, wherein the deliverables are selected from the group consisting of: a design document; a prototype; a source code for a web application; a source code for a native android application; a source code for an iOS application; a user manual; technical documentation of the software product; and a deployed application on a production server.
  • the organizing of the identified available resources around the software product engineering life-cycle plan for the software product includes forming a core team from the available resources and organizing the core team as at least a core portion of a captive team for the customer.
  • the core team includes core team members h aving domain-specific experience.
  • the organizing of th e identified available resources around the software product engineering life-cycle plan for the software product further includes performing of a Pod setup process to form a Pod from the available resources and organize the Pod as the captive team for the customer.
  • the Pod setup process involves a Pod incubation and evolution process having an onboarding phase; a kick-start phase; a self-managed phase; and a graduation phase.
  • the onboarding phase of the Pod setup process includes: training the resources; drafting the functional specifications; completing a design; generating a prototype; and making architectural decisions for building the software product.
  • the kick-start phase of the Pod setup process includes; developing a minimal viable product (MVP); and then iterating and evolving the MVP to yield a final product.
  • the self-managed phase of the Pod setup process includes product development and testing
  • the product development and testing include scrum-based agile development.
  • the graduation phase includes migrating the resources from a work environment of the host organization to a work environment of the customer served by the host organization.
  • the onboarding phase begins at a first milestone and ends at a second milestone;
  • the kick-start phase begins at the second milestone and ends at a third milestone;
  • the self-managed phase begins at the third milestone and ends at a fourth milestone;
  • the graduation phase begins at the fourth milestone and ends at a fifth milestone; and the first milestone, the second milestone, the third milestone, the fourth milestone and the fifth milestone occur in the Pod setup process in temporal order based on an ordinal number of each milestone.
  • the Pod setup process includes a recruitment phase, wherein the recruitment phase is to begin prior to the first milestone. In embodiments, the recruitment phase is to begin about 3 months prior to the first milestone. In embodiments, the second milestone is to occur at about 1 month after the first milestone. In embodiments, the fourth milestone is to occur in a range between about 18 months and about 24 months after the first milestone.
  • the performing of the Pod setup process includes allocating qualified core team members from the available resources to the Pod as at least a core portion of the Pod. In embodiments, the core team members have at least the competency requirements for the core team members according to the software product engineering life-cycle pla for the software product.
  • the core portion of the Pod is about 20 percent of the maximum headcount of the Pod during the self-managed phase of the Pod incubation and evolution process.
  • the performing of the Pod setup process includes allocating qualified staff members from the available resources to the Pod as at least a staff portion of the Pod.
  • the qualified staff members have at least the competency requirements for the qualified staff members according to the software product engineering life-cycle plan for the software product.
  • the staff portion of the Pod is about 70 percent of the maximum headcount of the Pod during the self-managed phase of the Pod incubation and evolution process.
  • the performing of the Pod setup process includes allocating qualified specialists from the available resources to the Pod as at least a specialist portion of the Pod.
  • the qualified specialists have at least the competency requirements for the qualified specialists according to the software product engineering life-cycle plan for the software product.
  • the specialist portion of the Pod is about 10 percent of the maximum headcount of the Pod during the self-managed phase of the Pod incubation and evolution process.
  • a second aspect provided herein includes a product engineering platform for assisting a host organization to provide product engineering as a service to a customer of the host organization, comprising: a project module for initiating and managing a project by the host organization on behalf of the customer, wherein the project module is configured to determine resource requirements for developing a product based on specifications received from the customer of the host organization; a resource module configured to identify available resources in the pool of resources m the host organization with available competencies matching the resource requirements and to organize the identified available resources around a product engineering life-cycle for the product; and a training module configured to assess training needs for building the product and delivering required training content to resources developing the product.
  • the platform is to execute a set of workflow's selected from the group consisting of: determining ideas about the product; mapping competency requirements for building the product with a set of available competencies of available resources from the host organization; organizing the identified available resources around the product engineering life-cycle plan of the product, providing a set of training and development tools for the resources; and providing a developed product as an output.
  • the product engineering life-cycle plan includes project phases selected from the group consisting of: a prototyping and design phase; a development of a web application phase; a parall el development of a native android and an iOS application phase; a testing and quality analysis (QA) phase; and a hosting and a release phase.
  • the product engineering life-cycle plan has deliverables to be provided at an end of the project phases, wherein the deliverables are selected from the group consisting of: a design document; a prototype; a source code for a web application; a source code for a native android application; a source code for an iOS application; a user manual; technical documentation of the product; and a deployed application on a production server.
  • the platform further comprises a processing system for processing data related to the one or more projects, competencies of the resources from the host organization available to work on the one or more projects, and training tools or materials.
  • the platform further comprises memory to store computer-readable instructions and one or more physical processors that execute the computer-readable instructions.
  • the processing system includes a plurality of processors, wherein the processors operate in an individual or distributed manner.
  • the plurality of processors is disposed in the same computing device or wherein the plurality of processors is implemented in separate computing devices.
  • the plurality of processors is disposed in rack-mounted servers at one or more physical locations.
  • the project module includes interfaces for a user to take as input ideas for product development and initiate a project for the product development.
  • the project module includes interfaces to receive the specifications and wherein the project module initiates a project for development of the product.
  • the specifications include defining information about the product.
  • the specifications include: a brief or detailed description of an idea for the product; a problem to be addressed by the product; a scope of work; details about features of the product; or functional, technical and design preferences.
  • the specifications include a new' social networking application on a web application or through a mobile device for connecting doctors and healthcare professionals with patients.
  • features of the product in the specification are selected from the group consisting of: a landing page providing an overview of the application; a signup section to prompt a user of the product to register and login to the application; news feed showing interactions and posts shared by people within a network; a profile feature having a user’s photo, interests, contact information, professional and personal information; an announcements feature to post any announcements about projects, jobs, upcoming proposals, research opportunities, internship opportunities; a groups feature to form a close group to discuss topics and interests with likeminded people; a chat feature to exchange messages with other users in the network; a job posting to allow the user or the other users to post and apply for jobs; and an expert directory feature where the user or the other users may search for an expert with specializations in a specific vertical
  • the project module includes a planning module to use the specifications to enable a user to initiate a project and determine the competency requirements for building the product.
  • the planning module is to coordinate with the resource module to identify the available resources within the host organization with available competencies matching the resource requirements and to organize the identified available resources around the product engineering life-cycle plan for the product.
  • the planning module is to coordinate with the training module to assess training requirements for the resources based on the project and to plan a delivery of training content to the resources.
  • the training module includes an assessing module to coordinate with the planning module to assess the training requirements for resources assigned to the project.
  • the training module includes a delivery module to coordinate with the planning module to deliver the training content to the resources.
  • the assessing module and the delivery module are to coordinate with a learning management system of the host organization to assess the training requirements and to deliver the training content.
  • the training module provides continuous or need-based training for resources developing the product.
  • the required training for a resource may be assessed based on factors selected from the group consisting of: a technical capability, an experience level, and an expertise in a domain of the product.
  • the training content includes functional or technical training related to skills selected from the group consisting of: web development; mobile development; database administration; front-end or back-end development; design and user experience; computer languages; and frameworks.
  • the training content is related to a domain of the product. In embodiments, the training content is related to intellectual property. In embodiments, the training module is to coordinate with a learning management system of the host organization to deliver the training content to the resources. In embodiments, the learning management system has comprehensive content including audio-visual modules and wherein the training module delivers a subset of the comprehensive content selected based on projects. In embodiments, the planning module is to help the user to develop a detailed project plan to be shared with the customer of the host organization. In embodiments, the detailed project plan includes defined timelines, project phases, milestones and deliverables. In embodiments, the project module is to plan and to manage execution of the project across the entire product engineering life-cycle plan.
  • the project module is to: keep track of progress of project activities: report a status of the project activities with a user; and take feedback from the user at predefined stages across the product engineering life-cycle.
  • the project module includes a workflow module to support and manage workflows associated with the project and to help to execute the detailed project plan developed by a planning module.
  • the workflow module is to track a project process across the product engineering life-cycle and to update a workflow when certain predefined milestones are reached in a detailed project plan.
  • the project module includes a reporting module to provide status updates to a user of the platform.
  • the status updates include project progress data.
  • the status updates are to be shared w th the customer.
  • the project module includes a feedback module m communication with a user, wherein the feedback module is to receive feedback from a stakeholder, wherein the platform incorporates the feedback to improve the product.
  • the stakeholder is a user or a customer.
  • the project module is to generate a graphical user interface (GUI).
  • GUI graphical user interface
  • the GUI includes a performance dashboard.
  • the GUI includes a resource dashboard to display availability and utilization of the pool of resources in the host organization.
  • the resource module is to: keep records including competencies and availability of all of the resources; coordinate with the project module to determine appropriate resources based on the resource requirements determined by the project module; and organize the appropriate resources around the product engineering life-cycle plan.
  • the resource module includes a mapping module and an organizing module.
  • the mapping module coordinates with a planning module of the project module to identify and map the resource requirements for the project including competency requirements onto the available resources of the host organization and to identify appropriate resources to build a team for the project based on the appropriate resources.
  • the organizing module is to organize the identified appropriate resources around the product engineering life-cycle plan.
  • the training module is to: keep records of training requirements of the resources; and coordinate with the project module to provide the resources with training and development tools.
  • the platform further comprises a database for storing data related to projects, resources and training.
  • the resource module is further to build resource profiles in the database wherein the resource profiles include fields selected from the group consisting of: a resource ID; competencies; and past projects.
  • the platform further comprises a database including datastores selected from the group consisting of: a project datastore to store project-related data records; a resource datastore to store resource-related data records; and a training datastore to store training-related data records.
  • the database includes one or more computer-readable storage mediums; wherein the storage mediums are located at a single physical location or distributed at different physical locations; wherein the different physical locations include different servers or different data centers.
  • the project-related data records include a project record having fields selected from the group consisting of: a project identifier; a project type; required competencies, a resource identifier, and project metadata.
  • the project identifier includes a unique identifier that corresponds to the project.
  • the project type is selected from the group consisting of: a web application; a native mobile application; and a foreign exchange and remittance platform.
  • the required competencies are selected from the group consisting of: a language, a framework, a functional experience, and an expertise in a domain.
  • the resource identifier includes an identifier of a resource assigned to work on the project.
  • the resource-related data records include a resource record having fields selected from the group consisting of: a resource identifier; a project identifier; resource competencies, a training curriculum, and resource metadata.
  • the resource identifier includes a username or a resource-associated value.
  • the project identifier includes an identifier of a project or a list of identifiers of projects that the resource worked on.
  • the resource competencies are selected from the group consisting of: a language, a framework, a functional experience; and expertise m a domain.
  • the training curriculum includes identification of courses and learning activities undertaken by the resource.
  • the resource metadata includes a data the resource started at the host organization, or a number of years of experience attained by the resource.
  • the platform is to facilitate initiating and managing projects by the host organization on behalf of the one or more customers by mapping the resource profiles onto project profiles to identify available resources in the host organization having competencies matching project resource and competency requirements. In embodiments, the platform is to facilitate initiating and managing projects by the host organization on behalf of the one or more customers by providing the identified available resources with a set of training and development tools relating to a domain of the product. In embodiments, the platform is to interact with a set of user devices, carried by a user, over a network to manage projects for the customer of the host organization.
  • the platform is to be connected to a customer relationship management (CRM) system for managing customer data and managing interactions of the host organization with customers.
  • CCM customer relationship management
  • the project module is configured to provide a detailed project plan to the customer including a project timeline, resources, milestones and deliverables.
  • the project module is configured to provide a status report to the customer at predefined stages in the product engineering life-cycle plan providing details about project progress.
  • the project module is configured to receive feedback from the customer through the product engineering life- cycle and incorporate the feedback to iterate on the product.
  • the platform is connected to organizational systems through a network wherein the platform coordinates with the organizational systems.
  • the organizational systems are selected from the group consisting of: a human resources information system; a learning management system; and a marketing automation module.
  • the organizational systems are deployed on-premise within the host organization or hosted on cloud servers of a software as a service vendor.
  • the platform further comprises a network interface system including one or more devices to perform wired or wireless communication, wherein the wireless communication is selected from the group consisting of: WiFi communication and cellular communication.
  • a third aspect provided herein includes an architecture for a product developed by the product engineering platform of the second aspect operated by the host organization for the customer, the architecture comprising: an enabling layer having a closed processing architecture, wherein the enabling layer has capabilities that are only exposed to the host organization; a services layer having an open microservices and web services architecture, wherein the services layer is to expose a business functionality of the product and to facilitate providing services to other business applications and to build partnerships w th ecosystem partners; and a personalization layer including: a user-oriented functionality responsible for managing user interaction with the product, and interfaces for a design experience and for a user experience.
  • the enabling layer implements a core functionality of the product and encapsulates a business logic.
  • a fourth aspect provided herein includes a method for providing collaborative software product development delivered as a shared service to a customer of a host organization, comprising: determining resource requirements including competency requirements for building a software product based on product specifications received from the customer; identifying available resources in the host organization with the available resources having available competencies matching the competency requirements for building the software product; organizing the identified available resources around a product engineering life-cycle plan for the software product; forming squads representing self-contained units of resources for building product features, wherein each of the squads is to iteratively develop the product based on feedback received from the customer through the product engineering life-cycle; and staging a migration of one or more of the squads from the work environment of the host organization to the work environment of the customer served by the host organization.
  • the method further includes identifying, via a product engineering platform, a core team of resources and providing the resources with training.
  • the method further includes applying an Agile software development method by the core team.
  • the Agile software development method is a conceptual framework for undertaking a software engineering project to minimize project risk by developing the software product in iterations, wherein the iterations occur in time frame chunks, wherein each iteration has a duration ranging from about one week to about four weeks, wherein each iteration includes planning tasks, requirements analysis, design tasks, development tasks, tests, and documentation tasks; wiierem each iteration is to release a new' incremental functionality' or feature of the software product.
  • the squads include from 4 to 7 resources.
  • each of the squads has full responsibility for a portion of the functionality of the iteration of the software product.
  • the squads are to develop features selected from the group consisting of: a news feed feature, a chat feature, an announcement feature, a job posting feature, and an expert directory' feature.
  • a plurality' of squads is organized into a tribe to focus on a common business area and share learning among the projects.
  • the common business area is mobile.
  • multiple squads are organized into a chapter to w'ork on a common technical area and share knowledge between project teams.
  • the common technical area is backend development or database administration. It is to be understood that any elements of this fourth aspect disclosed herein may be combined together in any desirable manner and/or configuration.
  • FIG. i is a diagrammatic view that depicts a network computing environment for implementing a product engineering platform in accordance with the present disclosure.
  • FIG. 2 is a diagrammatic view that depicts methods for implementing a product engineering platform in accordance with the present disclosure.
  • FIG. 3 is a diagrammatic view that depicts exemplary system architecture for a product engineering platform in accordance with the present disclosure.
  • FIG. 4 is a diagrammatic view that depicts an exemplary schema of a project record in accordance with the present disclosure.
  • FIG. 5 is a diagrammatic view that depicts an exemplary schema of a resource record in accordance with the present disclosure.
  • FIG. 6A is a diagrammatic view that depicts a heterogeneous layered architecture of a product developed by an example of the product engineering platform in accordance with the present disclosure.
  • FIG. 6B is a diagrammatic view that depicts an exemplary financial technology application product developed by an example of the product engineering platform in accordance with the present disclosure.
  • FIG. 6C is a diagrammatic view that illustrates an example digital payment application product developed by an example of the product engineering platform in accordance with the present disclosure.
  • FIG. 7 is a diagrammatic view that depicts the resource management approach utilized by the product engineering platform and migration of resources from a work environment of the host of the platform to the work environment of a customer in accordance with the present disclosure.
  • FIG. 8 is a diagrammatic view 7 that depicts an example of a software product engineering life-cycle in accordance with the present disclosure.
  • FIG. 9 is a diagrammatic view that depicts an example of a capacity building approach that is different from the capacity building approach shown in FIG. 7 in accordance with the present disclosure.
  • FIG. 10 is a diagrammatic view that depicts managed migration from capti ve team to incubator-style shared office/workspace and domain-led innovation ecosystem.
  • FIG. 11 is a diagrammatic view that depicts methods for implementing a product engineering platform in accordance with the present disclosure.
  • Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of the many embodiments of the systems and methods disclosed herein.
  • FIG. 1 depicts a network computing environment with various information technology components, sub-components, circuits, modules, blocks, systems, sub systems, software, methods, services, processes, and other elements collectively referred to herein as the system 100.
  • the system 100 enables users 102 to initiate and manage one or more new product engineering projects on behalf of a customer by organizing the available product developers and other team members around a product engineering life- cycle plan for the product and providing such developers a set of training and development tools relating to one or more of the domains of the product.
  • a product engineering project may refer to an initiative for building a software product such as a desktop, web or mobile application around an idea.
  • Such projects may be undertaken by a host’s organization for a customer and may involve teams with competencies in a wide range of areas including design, development, architecture, hosting, intellectual property, and the like.
  • the system 100 may include capabilities for initiating and managing projects by the user 102 such as an employee, manager or administrator in the host organization, by building project profiles on the system 100 including details like project IDs, objectives, requirements, product domains, and the like.
  • the system 100 may include capabilities for initiating and managing projects by the user 102 by building resource profiles on the system 100 including details like resource ID, competencies, past projects, and the like.
  • the system 100 may include capabilities for initiating and managing projects by the user 102 by mapping the resource profiles onto project profiles to identify the resources in the host organization that have competencies matching project resource and competency requirements.
  • the system 100 may include capabilities for initiating and managing projects by the user 102 by organizing such resources around the product engineering life-cycle plan for the product and providing such resources with a set of training and development tools relating to the domain of the product.
  • the system 100 may include a product engineering platform 104 that interacts with a set of user devices 108 carried by the user 102 over a network 110 to manage projects for the customer or customers of the host organization.
  • the product engineering platform 104 may also be connected to a customer relationship management (CRM) system 112 for managing the data and interactions of the host organization with various customers.
  • CRM customer relationship management
  • the product engineering platform 104 includes a database 114 for storing data and a processing system 1 18 for processing such data related to product engineering projects from various customers of the host organization, competencies of the resources from the host organization available to work on the one or more projects, and training tools and/or materials.
  • the processing system 118 may include memory (e.g., random access memory (RAM) and/or read-only memory (ROM)) that stores computer-readable instructions and one or more physical processors that execute the computer-readable instructions.
  • the processors may operate in an individual or distributed manner.
  • the two or more processors may be m the same computing device or may be implemented in separate computing devices (e.g., rack-mounted servers at one or more physical locations).
  • the processing system 1 18 may execute a project module 120, a resource module 122, and a training module 124.
  • the product engineering platform 104 allows the user 102 to initiate and manage a new product engineering project using the project module 120, help allocate resources for such a project using the resource module 122 and manage all functional and domain training for such project using the training module 124
  • the project module 120 may include interfaces for the user 102 to take as input ideas for new product development and initiate a new project for the same.
  • the project module 120 further helps the user 102 in planning the project and managing execution of the project across the entire product engineering life-cycle, keeping track of progress of project activities and reporting the status of such activities with the user 102 and taking feedback fro the user 102 at various stages across the product lifecycle.
  • the resource module 122 keeps a record of competencies and availability of all the resources and coordinates with the project module 120 to determine the appropriate resources based on the project requirement and then organize the available resources around the product engineering life-cycle plan of the product.
  • the training module 124 keeps records of training requirements of the resources and coordinates with the project module 120 to provide the resources with any training and development tools.
  • the product engineering platform 104 may also be connected to organizational systems 128 through the network 110 and may coordinate with such systems.
  • organizational systems 128 include a human resources information system (HRIS) 130, a learning management system (LMS) 132 and a marketing automation software (marketer) 134.
  • HRIS human resources information system
  • LMS learning management system
  • marketer marketing automation software
  • the organizational systems 128 may be deployed on-premise within the organization or hosted on the cloud servers of a software as a service vendor.
  • the term“on-premise” means located on the premises of the organization.
  • FIG. 2 illustrates a method for delivering software product engineering as a service through coordinated development of human resources, product, and intellectual property in accordance with embodiments of the systems and methods disclosed herein.
  • the product engineering platform 104 may help the user 102 in a host organization deliver software product engineering services to a customer of the host organization.
  • the method includes presenting an interface to a user 102 in the host organization to receive specifications for a software product.
  • the specification may include a brief or detailed description of the new' product idea, the problem addressed by the new product, the scope of work, details about features of the new product to be built and so on.
  • platform 104 may communicate with the user 102 about the same.
  • the method includes determining resource requirements including competency requirements for building the software product based on the specifications received at 202.
  • the method includes identifying available resources in the host organization, the available resources having available competencies matching the competency requirements for building the software product.
  • the method includes organizing of the identified available resources around a software product engineering life-cycle plan for the software product.
  • the method includes providing a set of training and development tools for the identified available resources useful for developing the software product.
  • the method includes delivering the developed software product to the customer. In examples, customer feedback may be sought through the software product engineering life-cycle of the software product.
  • FIG. 3 depicts an example of system architecture of the product engineering platform 104 including various components, sub-components, sub-systems, software and other elements in accordance with embodiments of the systems and methods disclosed herein.
  • the product engineering platform 104 delivers product engineering as a service to customers of a host organization through coordinated development of human resources, product, and intellectual property on behalf of the customer of the host organization.
  • the platform 104 can include a set of workflow's including determining ideas about a product, mapping the competencies required for building the product with the set of competencies of available human resources from the host organization, organizing such resources around the product engineering life-cycle plan of the product, and providing a set of training and development tools for such resources and providing a developed product as an output.
  • the project module 120 of the product engineering platform 104 may coordinate key activities around the planning of new projects related to new product development, managing workflows and project execution, providing status updates about the progress of a project including communicating with users and customers for feedback.
  • the project module 120 may include interfaces that receive specifications for new' product development and initiate a new project for the same.
  • the specifications may provide critical or defining information about the product and may include a brief or detailed description of the new product idea, the problem addressed by the new product, the scope of work, details about features of the new product to be built, functional, technical and design preferences, and so on.
  • the specification may mention a new social networking application on a weh application or through a mobile device for connecting doctors and healthcare professionals with patients.
  • the specifications may provide the following list of features to be built: landing page providing an overview of the application, signup section prompting the user to register and login to the application, news feed showing the interactions and posts shared by people within the network, profile feature having user’s photo, interests, contact information, professional and personal information, announcements feature to post any announcements about projects, jobs, upcoming proposals, research opportunities, internship opportunities, groups feature to form a close group to discuss topics and interests with !ikeminded people, chat feature to exchange messages with other users in the network, job posting to allow the user or the other users to post and apply for jobs, and expert directory feature wiiere the user or the other users may search for an expert with specializations in a specific vertical.
  • a planning module 302 in the project module 120 may use the specifications to enable the user 102 to initiate a project and determine the resource requirements for building the product.
  • the planning module 302 may coordinate with the resource module 122 to identify the available human resources within the host organization with the required competencies and organize such resources around the product engineering life-cycle plan for the product.
  • the planning module 302 may also coordinate with training module 124 to assess training requirements for the resources based on the project and planning the delivery of such training to the resources.
  • the planning module 302 may also help the user 102 in developing a detailed project plan with clearly defined timelines, project phases, milestones and deliverables that may be shared with the customer of the host organization.
  • a workflow module 304 is configured to support and manage the workflows associated with a project and to help in executing the detailed project plan developed by the planning module 302, The workflow module 304 may, for example, track the project process across the product lifecycle and update the workflow wiien certain predefined milestones are reached in the detailed project plan.
  • a reporting module 308 provides status updates to the users 102 of platform 104 about the project progress that may be shared with customers.
  • a feedback module 310 of the project module 120 communicates with the user 102 to receive any feedback from the user, customer or arty other stakeholder and incorporate such feedback to improve the product.
  • the project module 120 may also generate various graphical user interfaces (GUIs), such as performance dashboards, resource dashboards showing the availability and utilization of various resources in the host organization.
  • GUIs graphical user interfaces
  • the planning module 302 may determine that the following resources are required for building the product: two healthcare business analysts to interface with the customer, two designers, one architect and product manager, three web developers with expertise in PythonTM and DjangoTM, two AndroidTM developers with expertise in JavaTM, two iOSTM developers with expertise in SwiffTM/Objective CTM, two database engineers with expertise in MySQL, three testing and QA engineers, one release engineer, and two development operations engineers.
  • the planning module 302 would then coordinate with the resources system to identify available resources in the host organization matching these roles.
  • the planning module may develop a plan where these twenty resources are organized across the product engineering life-cycle plan of six months starting with functional analysis and can include one or more of the prototyping and design phase, development of the web application phase, parallel development of native android and iOS application phase, testing and QA phase, and a hosting and a release phase.
  • the workflow' module 304 may track the project process across the product lifecycl e and update the workflow at the end of each phase while reporting module reports of such progress to the user 102. For example, assuming the functional analysis, prototyping and design phase lasts one month, the workflow module 304 and reporting module keep the user 102 updated about the same.
  • a feedback module 310 may keep communicating with the user 102 across all the different phases across the product lifecycle to receive feedback and iteratively build the product.
  • Some examples of deliverables provided at the end of different phases may include design documents, prototypes, source code for a web application, source code for native android and iOS applications, user manual, technical documentation of the product and deployed application on the production server.
  • the resource module 122 includes a mapping module 312 and an organizing module 314.
  • the mapping module 312 coordinates with the planning module 302 of the project module 120 to identify and map the competencies required for a project onto the available resources of the host organization to build a team for a project.
  • the organizing module 314 then organizes the identified resources around the product engineering life-cycle plan.
  • the training module 124 includes an assessing module 318 and delivery module 320.
  • the assessing module 318 coordinates with the planning module 302 of the project module 120 to assess the training needs of various resources assigned for a project.
  • the delivery module 320 then coordinates with the planning module 302 to deliver such training to the identified resources.
  • the assessing module 318 and the delivery' module 320 of the training module 124 may coordinate with the learning management system (LMS) 132 of the host organization for assessment of training needs and training delivery'.
  • LMS learning management system
  • the training module 124 may provide continuous or need-based training for the resources developing the product.
  • the training needs for a resource may be assessed based on different factors such as technical capability, experience, and expertise in the domain of the product to be developed.
  • the training content may include functional or technical training related to skills such as web development, mobile development, database administration, front-end or back-end development, design and user experience, languages such as C++TM, PythonTM, PHPTM, JavaTM, RubyTM, ScaiaTM and the like, frameworks such as DjangoTM, RailsTM and the like.
  • the training content may relate to the domain of the product.
  • the training module 124 of the product engineering platform 104 may coordinate with the learning management system (LMS) 132 of the host organization to delivering the training content to the resources w'orking on various projects.
  • LMS learning management system
  • the LMS 132 may have comprehensive content including audio-visual modules while training modules may include selected content based on projects.
  • the database 114 may include a project datastore 322, a resource datastore 324 and a training datastore for storing project-related data records, resource-related data records, and training-related data records, respectively.
  • the database 1 14 may include one or more computer-readable storage mediums (e.g., hard disk drives and-' or flash memory drives).
  • the storage mediums may be located at the same physical location or distributed at different physical locations (e.g., different servers and/or different data centers).
  • a network interface system 330 includes one or more devices that may perform wired or wireless (e.g., WiFi or cellular) communication
  • FIG. 4 depicts a project record 400 in accordance with embodiments of the systems and methods disclosed herein.
  • the project record 400 includes a project ID 402, a project type 404, required competencies 406, resource identifier 408, and any suitable project metadata 410.
  • the project ID 402 may include a unique identifier that corresponds to the project.
  • the project type 404 may include a web application, native mobile application, forex and remittance platform, and the like.
  • the required competencies 406 may include languages, frameworks, functional experience, domain expertise and the like.
  • the resource identifier 408 may include an identifier of a resource assigned to work on the project.
  • the metadata 410 may include a creation date.
  • FIG. 5 depicts a resource record 500 in accordance with embodiments of the systems and methods disclosed herein.
  • each resource record 500 can include a unique resource identifier 502, a project identifier 504, resource competencies 506, training curriculum 508, and resource metadata 510.
  • the unique resource identifier 502 may include a username or value.
  • the project identifier 504 may include an identifier of a project or a list of identifiers of projects that the resource worked on.
  • the resource competencies 506 may include languages, frameworks, functional experience, domain expertise and the like.
  • the training curriculum 508 may include identification of courses and learning activities undertaken by the resource.
  • the resource metadata 510 may include a date joined, years of experience attained by the resource, and the like.
  • FIG. 6A depicts a heterogeneous layered architecture 600 for a product developed by the product engineering platform 104 operated by a host for a customer in accordance with embodiments of the systems and methods disclosed herein.
  • the architecture 600 may include an enabling layer 602 with a closed processing architecture configured with certain capabilities that are exposed only to the host.
  • the enabling layer 602 may implement the core functionality of the product and encapsulates the business logic.
  • the enabling layer 602 may also implement functionalities like identity and profile management, security and privacy infrastructure, product topology , communication channels, and the like.
  • a services layer 604 may have an open microservices and web services architecture that may expose the business functionality' of the product and helps provide services to other business applications and build partnerships with the ecosystem partners.
  • a personalization layer 606 may include a user-oriented functionality responsible for managing user interaction with the product interfaces for the design and user experience.
  • FIG. 6B depicts an example of an architecture 600’ of a foreign exchange and remittance application developed by the product engineering platform 104 in accordance with embodiments of the systems and methods disclosed herein.
  • the architecture 600’ includes an enabling layer 602’ with a closed processing architecture configured with capabilities listed that are exposed only to the host.
  • the enabling layer 602’ implements th e core functionality of the product and encapsulates the business logic.
  • the enabling layer 602’ also implements functionalities like identity and profile management, security' and privacy infrastructure, product topology', communication channels, and the like.
  • a services layer 604’ has an open microservices and web services architecture that exposes the business functionality of the product and helps provide services to other business applications and build partnerships with the ecosystem partners.
  • a personalization layer 606’ includes a user-oriented functionality responsi ble for managing user interaction with the product, interfaces for the design and user experience.
  • FIG. 6C depicts an example of an architecture 600” of a digital payment application developed by the product engineering platform 104 in accordance with embodiments of the systems and methods disclosed herein.
  • the architecture 600” includes an enabling layer 602” with a closed processing architecture configured with capabilities listed that are exposed only to the host.
  • the enabling layer 602 implements the core functionality of the product and encapsulates the business logic.
  • the enabling layer 602 also implements functionalities like identity and profile management, security and privacy infrastructure, product topology, communication channels, and the like.
  • a services layer 604” has an open microservices and web services architecture that exposes the business functionality of the product and helps provide services to other business applications and build partnerships with the ecosystem partners.
  • a personalization layer 606 includes a user-oriented functionality responsible for managing user interaction with the product, interfaces for the design and user experience.
  • FIG. 7 depicts an example of a resource management approach utilized by the product engineering platform and migration of resources from a work environment of the host of the platform to the work environment of a customer m accordance with embodiments of the systems and methods disclosed herein.
  • the product development process includes identifying the core team 702 of resources assigned to work on the new' project.
  • the core team 702 may be organized along the product engineering life-cycle 703 and the new product development process can be initiated.
  • the onboarding phase 704 of the product engineering life-cycle plan may involve trainin 718 the resources 716, drafting the product specifications (PS) or functional specifications (FS) 720, completing design and prototyping and defining an architecture 722 for the product.
  • the kick-start phase 708 begins the development process starting with the development of a minimal viable product (MVP) 724 and then iterating and evolving this MVP version to yield a final product.
  • MVP minimal viable product
  • the product development and testing 726 continue in self-managed phase 710 utilizing software development methodologies including scrum-based agile development.
  • hie resources 716 may be migrated from the work environment of the host organization to the work environment of the customer served by the host organization in the graduation phase 712.
  • the organizing of the identified available resources around the software product engineering life-cycle plan for the software product 208 includes forming a core team 702 from the available resources and organizing the core team 702 as at least a core portion of a captive team for the customer.
  • the core team 702 includes core team members having domain-specific experience.
  • the organizing of the identified available resources around the software product engineering life-cycle plan for the software product 208 further includes performing of a Pod setup process as depicted in FIG. 7 to form a Pod 728 from the available resources and organize the Pod as the captive team for the customer.
  • the Pod setup process involves a Pod incubation and evolution process 730 having an onboarding phase 704; a kick-start phase 708; a self-managed phase 710; and a graduation phase 712.
  • the onboarding phase 704 of the Pod setup process includes: training 718 the resources; drafting the functional specifications 720; completing a design 732; generating a prototype; and making decisions about architecture 722 for building the software product.
  • the kick-start phase 708 of the Pod setup process includes: developing a minimal viable product (MVP) 724; and then iterating and evolving the MVP to yield a final product.
  • the self-managed phase 710 of the Pod setup process includes product development and testing 726.
  • the onboard g phase 704 begins at a first milestone T1 and ends at a second milestone T2
  • the kick-start phase 708 begins at the second milestone T2 and ends at a third milestone T3.
  • the self-managed phase 710 begins at the third milestone T3 and ends at a fourth milestone T4.
  • the graduation phase 712 begins at the fourth milestone T4 and ends at a fifth milestone T5. It is to be understood that the first milestone Tl, the second milestone T2, the third milestone T3, the fourth milestone T4 and the fifth milestone T5 occur in the Pod setup process in temporal order based on an ordinal number (i.e., first, second, third, fourth, and fifth) of each milestone.
  • the Pod setup process includes a recruitment phase, wherein the recruitment phase is to begin prior to the first milestone TL In embodiments, the recruitment phase is to begin about 3 months prior to the first milestone Tl. In embodiments, the second milestone T2 is to occur at about 1 month after the first milestone Tl. In embodiments, the fourth milestone T4 is to occur in a range between about 18 months and about 24 months after the first milestone TL
  • the cross- hatched bars above the long arrow' at reference numeral 730 indicate the evolution of the Pod beginning with core team members and ending with the Pod.
  • the onboarding phase 704 between the first milestone Tl and the second milestone T2, only core team members are allocated to the project.
  • the kick-start phase 708 between milestone T2 and milestone T3, the evolution from the core team to the Pod is about 25 percent complete - as depicted by the cross-hatched bar being about 75% core team cross-hatch and 25% Pod cross-hatch.
  • FIG. 7 also illustrates a capacity-building approach as disclosed herein.
  • the onboarding phase 704, the kick-start phase 708, and the self-managed phase 710 each have a corresponding qualification mix 750, 750’ 750”.
  • the qualification mix 750, 750’, 750” is expressed as a fraction of the maximum headcount of the Pod during the self- managed phase of the Pod incubation period.
  • the performing of the Pod setup process includes allocating qualified core team members from the available resources to the Pod 728 as at least a core portion of the Pod 728.
  • the core team members have at least the competency requirements for the core team members according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the core team members may include domain- specific experience.
  • qualification mix 750 has a value of 2, which indicates that the core portion of the Pod 728 is about 20 percent of the maximum headcount of the Pod 728 during the self-managed phase 710 of the Pod incubation and evolution process.
  • the performing of the Pod setup process includes allocating qualified staff members from the available resources to the Pod 728 as at least a staff portion of the Pod 728.
  • the qualified staff members have at least the competency requirements for the qualified staff members according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the qualified staff members may include basic training such as training that may be obtained in a formal education seting such as a university or college in an undergraduate degree program. In FIG.
  • qualification mix 750 has a value of“2,7” which indicates that the core portion of the Pod 728 is about 20 percent, and the staff portion of the Pod 728 is about 70 percent of the maximum headcount of the Pod 728 during the self-managed phase 710 of the Pod incubation and evolution process.
  • the performing of the Pod setup process includes allocating qualified specialists from the available resources to the Pod 728 as at least a specialist portion of the Pod 728.
  • the qualified specialists have at least the competency requirements for the qualified specialists according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the qualified specialists may include project-specific experience and/or training such as an understanding of unique aspects of the software product under development in the project. In FIG.
  • qualification mix 750 has a value of“2,7,1” which indicates that the core portion of the Pod 728 is about 20 percent, the staff portion of the Pod 728 is about 70 percent, and the specialist portion of the Pod 728 is about 10 percent of the maximum headcount of the Pod 728 during the self-managed phase 710 of the Pod incubation and evolution process.
  • the product engineering life-cycle 703 may include: product specification and product management 734; functional analysis & design 736; architecture (software, solution & technology) 738; design, develop, test & deliver 740, quality assurance (QA) / user acceptance testing (UAT) 742; and hosting 744.
  • the core team 702 of resources that may be identified by the product engineering platform may first be provided with the requisite training and then organized along the product engineering life-cycle 703.
  • the Agile software development method may be used by the core team 702.
  • the Agile method is a conceptual framework for undertaking software engineering projects and minimizes project risk by developing software in short time frame chunks, called iterations, which typically last for one to four weeks.
  • An iteration includes the planning, requirements analysis, design, development, testing, and documentation tasks necessary to release a new incremental functionality or feature of the product and is itself a miniature software project.
  • the project resources may be split into small scrum teams or squads 714 of about 5-6 resources that own a small functionality end to end.
  • the squads 714 may have from about 4 to about 7 resources.
  • scrum teams or squads 714 may be formed for developin different features like news feed, chat, announcements, job postings, or expert directory features.
  • Such resource management and organizational approach may help in promoting team collaboration and innovation. For example,‘tribes’ which is a collection of squads focusing on the same business area like‘mobile,’ may be formed for helping share learnings from various projects. Similarly,‘chapters’ which is a collection of squads working in the same technical area like‘backend development’ or ‘database administration/ may be formed for helping cross-pollination between project teams.
  • FIG. 8 is a diagrammatic view that depicts an example of a software product engineering life-cycle 803 in accordance with the present disclosure.
  • the software product engineering life-cycle 803 begins with a concept 812.
  • the concept 812 feeds the design 802.
  • the architecture 804 is based on the design 802.
  • the software product is fully developed in the development 807 phase.
  • the software product is ready for hosting 810. Feedback is provided during any portion of the software product engineering life-cycle 803, thereby generating new concepts 812 and starting a new software product engineering life-cycle 803.
  • FIG. 9 is a diagrammatic view that depicts an example of a capacity-building approach that is different from the capacity building approach shown in FIG. 7 in accordance with the present disclosure.
  • the percentages (70%, 20%, and 10%) shown in FIG. 9 are percentages of the maximum headcount of the Pod.
  • the performing of the Pod setup process includes allocating qualified staff members 916 from the available resources to the Pod.
  • the qualified staff members 916 have at least the competency requirements for the qualified staff members according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the qualified staff members 916 may include basic training such as training that may be obtained in a formal education setting such as a university or college in an undergraduate degree program.
  • the performing of the Pod setup process includes allocating qualified core team members 918 from the available resources to the Pod as at least a core portion of the Pod.
  • the core team members have at least the competency requirements for the core team members 918 according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the core team members 918 may include domain-specific experience.
  • FIG. 9 indicates that qualified core team members 918 account for 20 percent of the maximum headcount of the Pod.
  • the performing of the Pod setup process includes allocating qualified specialists 920 from the available resources to the Pod as at least a specialist portion of the Pod.
  • the qualified specialists 920 have at least the competency requirements for the qualified specialists 920 according to the software product engineering life-cycle plan for the software product.
  • the competency requirements for the qualified specialists 920 may include project-specific experience anchor training such as an understanding of unique aspects of the software product under development in the project.
  • FIG. 9 indicates that qualified specialists 920 account for 10 percent of the maximum headcount of the Pod. As indicated in Fig. 9, the qualified specialists have joined the Pod and the Pod is at full strength at the third milestone T3.
  • FIG. 10 is a diagrammatic view that depicts managed migration from capti ve team to incubator-style shared office/workspace and domain-led innovation ecosystem.
  • the first phase Qi extends from the start of the project to Month 12.
  • the symbol at reference numeral 1020 stands for Product Engineering as a Service. As shown in FIG. 10, Product Engineering as a Service 1020 manages the Pod incubation and evolution process to deliver an array of Pods 1022.
  • the symbol at reference numeral 1024 stands for a captive product development teams as disclosed herein.
  • the symbol at reference numeral 1026 stands for a software product engineering life-cycle for example as shown in FIG. 8.
  • the symbol at reference numeral 1028 stands for the Enabling, Service, Personalization (ESP) architectural approach described herein with respect to FIG.
  • ESP Enabling, Service, Personalization
  • Capacity Building 1030 refers to the Pod Incubation and evolution process as shown in FIG. 7 and FIG. 9
  • the second phase ⁇ ? . extends from the Month 12 of the project to Month 24
  • Product Engineering as a Service 1020 manages the array of Pods 1022; and provides Business Intelligence (BI) and Analytics 1034 as a shared service.
  • BI Business Intelligence
  • FIG. 1 1 illustrates a method for providing collaborative software product development delivered as a shared service to a customer of a host organization in accordance with embodiments of the systems and methods disclosed herein.
  • the method includes determining resource requirements including competency requirements for building a software product based on product specifications received from the customer.
  • the method includes identify ing available resources in the host organization with the available resources having available competencies matching the competency requirements for building the software product.
  • the method includes organizing the identified available resources around a product engineering life-cycle plan for the software product.
  • the method includes forming squads representing self-contained units of resources for building product features, wherein each of the squads is to iteratively develop the product based on feedback received from the customer through the product engineering life-cycle.
  • the method includes staging a migration of one or more of the squads from the work environment of the host organization to the work environment of the customer served by the host organization
  • the present disclosure enables customers to build marquee software products and captive development teams while retaining critical intellectual property in the form of patents, products, and people.
  • the present disclosure enables the customer to leverage deep product engineering experience of the host organization, while optimizing resource utilization and managing migration to an incubator-style shared workspace.
  • the present disclosure enables the customer to build an innovation and product-centric culture focused on achieving the customer’s overall business goals
  • the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor.
  • the present disclosure may be implemented as a method on the machine, as a system or apparatus as part of or in relation to fte machine, or as a computer program product embodied in a computer-readable medium executing on one or more of the machines.
  • the processor may be part of a server, cloud server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platforms
  • a processor may be any kind of computational or processing device capable of executing program instructions, codes, binar' instructions and the like.
  • the processor may be or may include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon.
  • the processor may enable the execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application.
  • methods, program codes, program instructions and the like described herein may be implemented in one or more threads. The thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code.
  • the processor may include non-transitory memory that stores methods, codes, instructions and programs as described herein and elsewhere.
  • the processor may access a non-transitory storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere.
  • the storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory', hard disk, flash drive, RAM, ROM, cache and the like.
  • a processor may include one or more cores that may enhance speed and performance of a multiprocessor.
  • the processor may be a dual core processor, quad core processors, other chip-level multiprocessors and the like that combine two or more independent cores (called a die).
  • the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, client, firewall, gateway, hub, router, or other such computer and/or netwOrking hardware.
  • the software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server, cloud server, and other variants such as a secondar' server, host server, distributed server and the like.
  • the server may include one or more of memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like.
  • the methods, programs, or codes as described herein and elsewhere may be executed by the server.
  • other devices required for the execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
  • the server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, social networks, and the like. Additionally, this coupling and/or connection may facilitate remote execution of programs across the network. The networking of some or ail of these devices may facilitate parallel processing of a program or method at one or more locations without deviating from the scope of the disclosure.
  • any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions.
  • a central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.
  • the software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like.
  • the client may include one or more of memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like.
  • the methods, programs, or codes as described herein and elsewhere may be executed by the client.
  • other devices required for the execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
  • the client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of programs across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more locations without deviating from the scope of the disclosure.
  • any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions.
  • a central repository may provide program instructions to be executed on different devices.
  • the remote repository may act as a storage medium for program code, instructions, and programs.
  • the network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art.
  • the computing and/or non computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like.
  • the processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
  • SaaS software as a service
  • PaaS platform as a service
  • laaS infrastructure as a service
  • the methods, program codes, and instructions described herein and elsewhere may ⁇ be implemented on a cellular network having multiple cells.
  • the cellular network may either be frequency division multiple access (FDMA) netw'ork or code division multiple access (CDMA) network.
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like.
  • the cell network may be a GSM, GPRS, 3G, 4G, 5G, EVDO, mesh, or other netw ork types.
  • the mobile devices may include navigation devices, ceil phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic book readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices.
  • the computing devices associated with mobile devices may he enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices.
  • the mobile devices may communicate with base stations interfaced with servers and configured to execute program codes.
  • the mobile devices may communicate on a peer-to-peer network, mesh network, or other communications network.
  • the program code may he stored on the storage medium associated with the server and executed by a computing device embedded within the server.
  • the base station may include a computing device and a storage medium.
  • the storage device may store program codes and instructions executed by the computing devices associated with the base station.
  • the computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory- (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory'; optical storage such as CD, DVD; removable media such as flash memory (e.g., universal serial bus (USB) sticks or keys), floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory ' such as dynamic memory , static memory , read/ write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
  • RAM random access memory-
  • mass storage
  • the methods and systems described herein may transform physical and/or intangible items from one state to another.
  • the methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.
  • the elements described and depicted herein, including in flow charts and block diagrams throughout the figures, imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure.
  • machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipment, servers, routers, and the like.
  • the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions.
  • the methods and/or processes described above, and portions associated therewith, may be realized m hardware, software or any combination of hardware and software suitable for a particular application.
  • the hardware may include a general-purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing de vice.
  • the processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable devices, along with internal and/or external memory.
  • the processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine-readable medium.
  • the computer executable code may he created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programmin languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as wall as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.
  • a structured programming language such as C
  • an object oriented programming language such as C++
  • any other high-level or low-level programming language including assembly languages, hardware description languages, and database programmin languages and technologies
  • methods described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computin devices, performs the portions thereof.
  • the methods may be embodied in systems that perform the portions thereof and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware.
  • the means for performing the portions of the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.
  • performing the step of X includes any suitable method for causing another party such as a remote user, a remote processing resource (e.g., a server or cloud computer) or a machine to perform the step of X.
  • performing steps X, Y and Z may include any method of directing or controlling any combination of such other individuals or resources to perform steps X, Y and Z to obtain the benefit of such steps.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Development Economics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un procédé de distribution d'une ingénierie de produit logiciel en tant que service à un client par une organisation hôte qui comprend les étapes consistant à présenter une interface à un utilisateur dans l'organisation hôte pour recevoir des spécifications pour un produit logiciel, à déterminer des exigences de ressources comprenant des exigences de compétences pour la construction du produit logiciel sur la base des spécifications, à identifier des ressources disponibles dans l'organisation hôte, les ressources disponibles ayant des compétences disponibles correspondant aux exigences de compétences pour construire le produit logiciel, à organiser les ressources disponibles identifiées autour d'un plan de cycle de vie d'ingénierie de produit logiciel pour le produit logiciel, à fournir un ensemble d'outils d'apprentissage et de développement pour les ressources disponibles identifiées utiles pour le développement du produit logiciel, et à distribuer le produit logiciel développé au client.
PCT/US2019/066310 2018-12-14 2019-12-13 Systèmes et procédés d'ingénierie et de gestion de produit collaboratives WO2020123993A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201811047397 2018-12-14
IN201811047397 2018-12-14

Publications (2)

Publication Number Publication Date
WO2020123993A2 true WO2020123993A2 (fr) 2020-06-18
WO2020123993A3 WO2020123993A3 (fr) 2020-09-17

Family

ID=71077057

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/066310 WO2020123993A2 (fr) 2018-12-14 2019-12-13 Systèmes et procédés d'ingénierie et de gestion de produit collaboratives

Country Status (1)

Country Link
WO (1) WO2020123993A2 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114327378A (zh) * 2022-03-15 2022-04-12 广州弘一信息科技股份有限公司 一种基于软件开发的项目管理系统
CN114648317A (zh) * 2022-05-24 2022-06-21 智昌科技集团股份有限公司 基于微服务架构的产品供应调控系统及其方法
CN116757650A (zh) * 2023-08-21 2023-09-15 欧特朗(日照)云科技有限公司 一种基于机器学习的项目管理及资源调度的方法
US11811681B1 (en) 2022-07-12 2023-11-07 T-Mobile Usa, Inc. Generating and deploying software architectures using telecommunication resources
CN117938636A (zh) * 2024-03-25 2024-04-26 中国人民解放军国防科技大学 智能节点管控服务系统
US11977858B2 (en) 2022-02-07 2024-05-07 T-Mobile Usa, Inc. Centralized intake and capacity assessment platform for project processes, such as with product development in telecommunications
US20240250949A1 (en) * 2023-01-24 2024-07-25 DiverseCity, Inc. System for providing a diversity, equity, and inclusion information platform
US12164887B2 (en) 2022-07-12 2024-12-10 T-Mobile Usa, Inc. Identifying standards-related requirements for software architectures using telecommunication resources

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110154441A1 (en) * 2009-12-18 2011-06-23 Electronics And Telecommunications Research Institute Online development environment server, online marketplace server, online development environment constituting method, and developed application providing method
US20120143570A1 (en) * 2010-12-03 2012-06-07 University Of Maryland Method and system for ontology-enabled traceability in design and management applications
KR20130045464A (ko) * 2011-10-26 2013-05-06 박동화 온라인 네트워크상에서 보안처리된 개발도구를 이용한 협업작업 방식의 소프트웨어 제작과 관리에 관한 방법
WO2014065444A1 (fr) * 2012-10-23 2014-05-01 한국생산기술연구원 Système de collaboration utilisant un réseau public ouvert
US20150039357A1 (en) * 2013-07-31 2015-02-05 LivelyHood, Inc. Systems and Methods for Providing on Demand Business Resources

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11977858B2 (en) 2022-02-07 2024-05-07 T-Mobile Usa, Inc. Centralized intake and capacity assessment platform for project processes, such as with product development in telecommunications
CN114327378A (zh) * 2022-03-15 2022-04-12 广州弘一信息科技股份有限公司 一种基于软件开发的项目管理系统
CN114648317A (zh) * 2022-05-24 2022-06-21 智昌科技集团股份有限公司 基于微服务架构的产品供应调控系统及其方法
CN114648317B (zh) * 2022-05-24 2022-09-13 智昌科技集团股份有限公司 基于微服务架构的产品供应调控系统及其方法
US11811681B1 (en) 2022-07-12 2023-11-07 T-Mobile Usa, Inc. Generating and deploying software architectures using telecommunication resources
US12164887B2 (en) 2022-07-12 2024-12-10 T-Mobile Usa, Inc. Identifying standards-related requirements for software architectures using telecommunication resources
US20240250949A1 (en) * 2023-01-24 2024-07-25 DiverseCity, Inc. System for providing a diversity, equity, and inclusion information platform
CN116757650A (zh) * 2023-08-21 2023-09-15 欧特朗(日照)云科技有限公司 一种基于机器学习的项目管理及资源调度的方法
CN116757650B (zh) * 2023-08-21 2023-11-14 欧特朗(日照)云科技有限公司 一种基于机器学习的项目管理及资源调度的方法
CN117938636A (zh) * 2024-03-25 2024-04-26 中国人民解放军国防科技大学 智能节点管控服务系统
CN117938636B (zh) * 2024-03-25 2024-05-24 中国人民解放军国防科技大学 智能节点管控服务系统

Also Published As

Publication number Publication date
WO2020123993A3 (fr) 2020-09-17

Similar Documents

Publication Publication Date Title
WO2020123993A2 (fr) Systèmes et procédés d'ingénierie et de gestion de produit collaboratives
Yeh et al. Critical success factors for integrated library system implementation in academic libraries: A qualitative study
CN107665150A (zh) 用于计算机系统的事件服务建模框架
Eaidgah et al. Holistic performance management of virtual teams in third-party logistics environments
Haig-Smith et al. Cloud Computing as an Enabler of Agile Global Software Development.
Lundene et al. How autonomy emerges as agile cross-functional teams mature
EP2610796A1 (fr) Gestion d'un projet lors d'une transition
US20200395130A1 (en) Virtual advisory board
Prasher Internet of things (iot) and changing face of project management
Kamil Exploring the perceived success factors of agile software projects in Indonesian startups
Al Rashdan et al. Automated work packages: Capabilities of the future
Arman A practical strategic planning approach for R&D organisations
Jima et al. State of artificial intelligence eco-system in Ethiopia
Jadad-Garcia et al. The Foundations of Computational Management: A Systematic Approach to Task Automation for the Integration of Artificial Intelligence into Existing Workflows
Su et al. A Case Study of DevOps Adoption within a Large Financial Organisation
Brandao Cloud Computing and Distance Learning in Computer Science
Chenoweth et al. Crafting an Undergraduate Course at the Intersection of Machine Learning and Software Engineering
Mitrovic The impact of cloud computing on the role of an IT department: a case study of a higher education institution in the Western Cape
Gupta et al. Creating the 24-hour knowledge factory
Kempegowda Enterprise architecture driven approach for digital transformation of modern organization
Kahn We are not alone: The intersection of project management and content strategy
Norbert Jr et al. Barriers impeding knowledge management for hardware integration and engineering teams
Munoz Digital prowess: Technology skills expectations in the contemporary workplace
Smit DANS Self-Evaluation-Report 2024
Bari et al. Managing knowledge in development of agile software

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19896782

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19896782

Country of ref document: EP

Kind code of ref document: A2

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载