Abstract: The present embodiment provides a system (100) for collaboratively viewing software development in real-time. The system includes a specs module (102), a design module (104) and a preview module (106). The present embodiment automatically develops the software in real-time while combining with the collaborative iterations that is visible to all stakeholders. Reference Figure 1
DESC:FIELD OF INVENTION
The present embodiment relates to a system for automatic software development, and more particularly relates to the system for collaboratively viewing the software development in real-time.
BACKGROUND OF THE INVENTION
In today’s world, software is needed in almost in almost every business and industry ranging from local retailers to hospitals and multi-national companies. Business enterprises rely on increasingly sophisticated software to manage their internal operation and provide goods and services to their clients and customers.
Traditionally, software development was done manually and involved extensive coding and a large team to run and manage the software. The software usually comprises of a large number of lines of computer code.
Recently, a few of the systems are developed for the automatic development and deployment of the software. However, the problem associated with these systems is that the different users are unable to see the work progress of the software development. For example, project managers may not know what the domain analyst is performing. This leads to a variety of disadvantages vis-à-vis a difference in the understanding of the requirements, skill and experience among team members, delay in creating infrastructure, delay in developing and releasing each iteration of the software development, delay in prototype development and communication gap among the team members.
Therefore, there is a need of a system that helps in overcoming the disadvantages of the available systems and approaches for software development process. There is also a need of the system that combines the collaborative iterations and automatic software development for viewing the work progress by the different users.
OBJECTIVES OF THE INVENTION
An objective of the present embodiment is to reduce communication gap among the team members.
Another objective of the present embodiment is to automatically develop the software in real-time while combining the collaborative iterations that is visible to all stakeholders.
Yet another objective of the present embodiment is to reduce fatigue from continuous iterations.
SUMMARY OF THE INVENTION
In an aspect, a computer-implemented system (100) for automatic software development collaboratively and interactively in real-time is provided. The computer-implemented system includes a specs module, a design module and a preview module.
The specs module captures a user input and represents the in a standard format. The user input is a text, a speech, a chatbot, an image, a video, an interview and a document.
The design module displays a design, an architecture and configuration parameters of the developing software. The software design is developed through a variety of mathematical and software engineering concepts.
The preview module helps in previewing the developed software. The preview module (106) provides a variety of templates of UI for forms, reports dashboards and websites.
The preceding is a simplified summary to provide an understanding of some aspects of embodiments of the present invention. This summary is neither an extensive nor exhaustive overview of the present invention and its various embodiments. The summary presents selected concepts of the embodiments of the present invention in a simplified form as an introduction to the more detailed description presented below. As will be appreciated, other embodiments of the present invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
The above and still further features and advantages of embodiments of the present invention will become apparent upon consideration of the following detailed description of embodiments thereof, especially when taken in conjunction with the accompanying drawings, and wherein:
Figure 1 illustrates a computer-implemented system (100) for automatic software development collaboratively & interactively in real time, according to an embodiment herein; and
Figure2 illustrates an example of the computer-implemented system (100) for automatic software development collaboratively & interactively in real time, according to an embodiment herein.
To facilitate understanding, like reference numerals have been used, where possible, to designate like elements common to the figures.
DETAILED DESCRPTION
As used throughout this application, the word "may" is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including but not limited to.
The phrases “at least one”, “one or more”, and “and/or” are open-ended expressions that are both conjunctive and disjunctive in operation. For example, each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B, or C” and “A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
The term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including”, and “having” can be used interchangeably.
Figure 1 illustrates the computer-implemented system (100) for automatic software development collaboratively & interactively in real-time. The present computer-implemented system (100) combines collaborative iterations and automatic software development for viewing work progress by different users in real-time. The present computer-implemented system (100) includes a specs module (102), a design module (104) and a preview module (106).
The computer-implemented system (100) may be implemented/hosted on an electronic device such as, but not limited to, a server, a laptop, a computer, a mobile phone and a tablet. The computer-implemented method (100) does not require any coding for the development of the software.
The specs module (102) is configured to capture a user input and re-present the user input in a standard specification. In an embodiment, the user input may be of a variety of formats such as, but not limited to, a text, a speech, a chatbot, an image, a video, an interview and a document.
The user input is processed through artificial intelligence based Natural Language Processing (NLP) to convert into a blueprint of the required software. In an embodiment, the blueprint may be in terms of normalized fundamental software elements and/or an abstract design element. In an embodiment, the normalized fundamental software element and the abstract design element are stored in a database. In another embodiment, the normalized fundamental software elements and the abstract design elements are stored in a file format such as, but not limited to, JSON/XML.
The abstract design element blueprint of the software is the basic element on which the specs module (102), the design module (104) and the preview module (106) build their respective views. A software requirement specification (SRS) is automatically generated through the blueprint of the software. In an embodiment, the SRS document is in a standard format such as IEEE SRS format.
In an embodiment, the specs module (102) is a user-friendly module and may be of use to business stakeholders, domain experts and domain analysts.
The design module (104) is configured to instantaneously display a design, an architecture and configuration parameters of the intended software. The design may include High Level Design (HLD) as well as Low Level Design (LLD). HLD such as architectural design, system design etc. and LLD such as component design, object design, packaging structure and other LLDs such as UML diagrams, document, drawings. In an embodiment, the design module (104) displays the software architecture in graphical UI format in real-time. The design module (104) builds the software architecture and parameters based on the blueprint generated by the specs module (102). In an embodiment, the software design is developed through a plurality of mathematical and software engineering concepts such as, but not limited to, Domain-Driven Design (DDD), Normalized Systems Theory (NST) Data, Context and Interaction (DCI), Object Oriented Concepts & Patterns.
In an embodiment, DDD effectively captures the high level structure and the low level structure of the software using entity, attributes, aggregate and value objects. In another embodiment, DDD captures the behavior of the software with event, action, task and process.
In an embodiment, NST and DCI are patterns that enable automatic generation of software code that is not only as per the users input requirement but is also highly evolvable and highly reusable.
In an embodiment, any change made in the design module (104) will be reflected real-time in the blueprint of the software. In an embodiment, the design module (104) is a user-friendly module and may be of use to architects and project managers.
The preview module (106) is configured to display the developed software to the extent the requirements are provided by the user in the specs module (102). The software in the preview module (106) is automatically generated from the blueprint of the specs module (102). In an embodiment, the preview module (106) may provide a variety of templates of UI for forms, reports, dashboards and websites. In an embodiment, the preview module (106) is a user-friendly module and may be of use to quality assurance member, UI designer and end-users.
In an embodiment, the specs module (102), the design module (104) and the preview module (106) is a display device. In an embodiment, the display device includes a laptop, a computer, a mobile phone and a tablet. In an embodiment the specs module (102), the design module (104) and the preview module (106) may be provided as a split-window view for different users to know the activity that is happening by the other users in real-time. For example, the users of the preview module (106) can see the activities of the users at the specs module (102) in real-time. The specs module (102), the design module (104) and the preview module (106) work in parallel and provide different views of the software development i.e. specifications, design, and the end-user software in real-time.
For example, when a business user provides following input in the specs module (102) (for an intended software system such as HR software)
“Each Employee will be identified by an Employee Code”
Specs module (102) will convert the natural language input into standard requirements specifications such as IEEE SRS format as
“Employee Code can be captured, saved, edited, viewed, deleted and exported in the system”
In the design module (104), the Employee entity will be qualified with the CODE attribute and represented graphically (shown in Figure 2).
Simultaneously, the preview module (106) will present the auto-built software for the user to interact with. The user may select any template in the Preview module which will update the specs module and the design module.
Similarly, the user may modify the drag-n-drop interactive design which will simultaneously reflect on specs module and preview module.
In an embodiment, the specs module (102), the design module (104) and the preview module (106) may be viewed as one browser with different tabs of the specs module (102), the design module (104) and the preview module (106), three different browsers and/or windows of the specs module (102), the design module (104) and the preview module (106) and physically separated different screens/windows for the specs module (102), the design module (104) and the preview module (106).
The foregoing discussion of the present invention has been presented for purposes of illustration and description. It is not intended to limit the present invention to the form or forms disclosed herein. In the foregoing Detailed Description, for example, various features of the present invention are grouped together in one or more embodiments, configurations, or aspects for the purpose of streamlining the disclosure. The features of the embodiments, configurations, or aspects may be combined in alternate embodiments, configurations, or aspects other than those discussed above. This method of disclosure is not to be interpreted as reflecting an intention the present invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment, configuration, or aspect. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of the present invention.
Moreover, though the description of the present invention has included description of one or more embodiments, configurations, or aspects and certain variations and modifications, other variations, combinations, and modifications are within the scope of the present invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.
,CLAIMS:WE CLAIM:
1. A computer-implemented system (100) for automatic software development collaboratively and interactively in real-time, the computer-implemented system (100) includes:
- a specs module (102) is configured to capture a user input and represent the input in a standard format, wherein the user input is a text, a speech, a chatbot, an image, a video, an interview and a document;
- a design module (104) is configured to display a design, an architecture and configuration parameters of the developing software, wherein the software design is developed through a variety of mathematical and software engineering concepts; and
- a preview module (106) is configured to preview the developed software, wherein the preview module (106) provides a variety of templates of UI for forms, reports dashboards and websites.
2. The computer-implemented system (100) as claimed in claim 1, wherein the specs module (102) processes the user input through artificial intelligence based Natural Language Processing (NLP) to convert into a blueprint of the required software.
3. The computer-implemented system (100) as claimed in claim 1, wherein the variety of mathematical and software engineering concepts includes Domain-Driven Design (DDD), Normalized Systems Theory (NST) Data, Context and Interaction (DCI), Object Oriented Concepts & Patterns.
4. The computer-implemented system (100) as claimed in claim 1, wherein the software design is High Level Design (HLS) and Low Level Design (LLD).
5. The computer-implemented system (100) as claimed in claim 1, wherein the specs module (102), the design module (104) and the preview module (106) works in parallel and provide different views of the software development.
6. The computer-implemented system (100) as claimed in claim 1, wherein the specs module (102), the design module (104) and the preview module (106) is provided as a split-window view for different users to know the activity that is happening by the other users in real-time.
| # | Name | Date |
|---|---|---|
| 1 | 202241031886-STATEMENT OF UNDERTAKING (FORM 3) [03-06-2022(online)].pdf | 2022-06-03 |
| 2 | 202241031886-PROVISIONAL SPECIFICATION [03-06-2022(online)].pdf | 2022-06-03 |
| 3 | 202241031886-PROOF OF RIGHT [03-06-2022(online)].pdf | 2022-06-03 |
| 4 | 202241031886-POWER OF AUTHORITY [03-06-2022(online)].pdf | 2022-06-03 |
| 5 | 202241031886-FORM FOR SMALL ENTITY(FORM-28) [03-06-2022(online)].pdf | 2022-06-03 |
| 6 | 202241031886-FORM FOR SMALL ENTITY [03-06-2022(online)].pdf | 2022-06-03 |
| 7 | 202241031886-FORM 1 [03-06-2022(online)].pdf | 2022-06-03 |
| 8 | 202241031886-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [03-06-2022(online)].pdf | 2022-06-03 |
| 9 | 202241031886-EVIDENCE FOR REGISTRATION UNDER SSI [03-06-2022(online)].pdf | 2022-06-03 |
| 10 | 202241031886-DRAWINGS [03-06-2022(online)].pdf | 2022-06-03 |
| 11 | 202241031886-DECLARATION OF INVENTORSHIP (FORM 5) [03-06-2022(online)].pdf | 2022-06-03 |
| 12 | 202241031886-DRAWING [05-06-2023(online)].pdf | 2023-06-05 |
| 13 | 202241031886-COMPLETE SPECIFICATION [05-06-2023(online)].pdf | 2023-06-05 |
| 14 | 202241031886-FORM 18 [13-09-2023(online)].pdf | 2023-09-13 |
| 15 | 202241031886-FER.pdf | 2025-04-11 |
| 16 | 202241031886-FER_SER_REPLY [08-10-2025(online)].pdf | 2025-10-08 |
| 1 | Search031886E_15-07-2024.pdf |