Enterprise Requirements Engineering
For enterprises that need to compute standardised software requirement specifications (SRS) documents according to abac’s requirement engineering process.
Software Requirement Specification Construction
SRS (IEEE 29148) documents represent a standardised way in which to describe the features needed by a software system. With this is mind, abac works together with enterprises for structuring the requirements of the to-be-built system.
Process
As industries run on concrete processes that are optimised by software, abac ensures it’s own processes used for the manufacturing of software solutions are as transparent and intuitive as possible.
Conceptual knowledge share
A series of meetings will ensure that the context for optimisation is well understood by abac
Collaborative documentation
The functional and non-functional requirements that describe the to-be-built software system are collaborativelly documented out by abac
Functional Prototyping
A functional prototype (or wireframe) will be constructed by abac in order to conceptually understand the way in which the system's users will make use of the application.
SRS Elaboration
The Software Requirement Specification (SRS) document will be aggregated, versioned and delivered to the stakeholders of the project.
Feedback
As a manufacturer of software solutions, it is our full intent that the resulteing systems help enterprises optimise operations and grow incrementally. As such, abac shares in both an enterprise’s problems and it’s solutions, with great interest.
Enterprise Requirements Engineering
Get a complete documentation for what your software system should look, feel and function by working with a company that will own up to your mission.
Frequently asked questions
How are custom software applications manufactured?
Each custom build software application has to undergo a software development process before it can reach market-readiness.
As such, the following video explains the lifecycle for a software application.
Software systems, API's, applications and other technical jargon?
A software application
A software application (or app) is practically a computer program that is designed for satisfying a specific purpose for a specific series of users.
Frontend applications
Frontend applications (or client applications) are applications that have user interfaces. Think of a website, a mobile app or a desktop program that you can work with.
Backend applications
Backend applications are applications that just contain business specific logic (data-centric apps, apis) and that allow other applications to interact with this logic.
An API (or Application Programming Interface) is a good example for an application that exposes business logic towards being used by other applications.
A software system
A software system is practically a collection of applications and apis that work together towards solving a particular set of problems.
Custom software development vs web-design?
If you’re in need of a simple presentational website or a simple e-commerce store then you’re in need of webdesign services that help you build your web experience of top of an existing software platform (such as wordpress or instacart, which offers a lot of software features out of the box)
Custom software development on the other hand represents the manufacturing of software applications that may have unique busines logic (that hasn’t existed before).
Custom developed software systems allow for far greater flexibility with regards to the detail of customisation.
Creating a web application for orchestrating the workflow of your specific business or manufacturing a software product that is unique to your vision are great examples of what the yield of custom software development is.
How much time does is take to build a web system?
În general, the amount of effort that goes into the creation of a custom build software system depends on the number of features that are needed.
As a simple rule of thumb, we have created a simple T-Shirt size for how much time it takes to develop certain systems:
- S –> Software systems that require a period of 1-3 months to reach the first releasable version
- M –> Software systems that require a period of 3-6 months to reach the first releasable version
- L –> Software systems that require a period of 6-12 months to reach the first releasable version
- XL –> Software systems that require a period of more than 12 months to reach the first releasable version
How is effort estimated for developing bespoke software solutions?
The way in which estimation is performed varies from company to company.
At abac, we make use of an estimation system that involves scoring software features using complexity points and then amounting these complexity points into a total.
By dividing this total against the number of points that a particular team can develop in a certain perioad of time, we then find out the number of weeks needed in order to implement the software solution.
How much does a simple MVP web app cost?
Web applications vary quite a lot depending on industry of use and purpose. În general, an MVP version of an web app will cost you around 20.000$ – 30.000$