• Increase font size
  • Default font size
  • Decrease font size
Home Features
Our Expertise E-mail
Article Index
Our Expertise
Graphics designing
Software Development
System Annalysis
All Pages
  • >E-Commerce,Web & E-Mail Hosting 
    >Digital Strategy
    >Creative Design
    > Integrated Advertising & Marketing
    >Search Engine Optimization
    > Online Marketing
    >Wireless Marketing

  • Graphics designing

Our Graphic Designers find the best way to communicate a message by using print, electronic and film media through evaluating color, type, illustration, photography, animation and other print techniques. Our Graphic Designers whom we are associated with also plan the layout and production of magazines, newspapers, journals and corporate reports. They produce promotional material such as displays, packaging or marketing brochures, and they design logos for products and businesses. They also play a key role in duties related to having best grapghics also included in designing websites, interactive media, and multimedia projects.

  • WebDesigning
    Internet is the fastest growing informative medium today, simply because many prospects prefer spending more time online and published content is always available at their convenience.   

    It makes infinite sense to invest in the World Wide Web given that it’s cheap and information can be accessed at any location. If targeted correctly and messages crafted aptly, a web portal can help you deliver the right content to the right segment at the right time hence achieving high response. Our Web solution will  potray to you a focalpoint concept full of warm and eye appealing user interface. We will create a banner that potray the desires of visitors who come to the site and ensure that it communicates the right message to them.

    We use expandable (tree-type) menus on the left menu which will reduce congestion on the first page. These menus will ensure that users easily navigate through the site and access relevant information without any hustle.

    Within the website we will have specific section which will be designated for banner advertisement. Flashy banners with roll over images will be used. These banners will brighten the site and also create revenue for sustenance of the website.

    To collect user views, we will incorporate polls and forums which users will be able to post theirs feeling about the site.

    A newsletter system is also incoperated.


  • Content Management System
    The right Content Management System (CMS) can make all the difference. A CMS can reduce site maintenance costs and web publishing-based IT operations costs by a third, and can cut the labor cost for content authoring and design in half.

    The benefits of deploying a web content management system are many, including: money saved on materials and resources allocated to the creation and maintenance of Web site content; a consistent look, feel, and brand image across Web sites; automating manual site management tasks; automated content scheduling and expiration; simplified deployment of new sites and sub-sites; full content audit capabilities; content recall and rollback for version control; reduced training costs.

    As we implement the web solution for solution we intend to incorporate, a content management system that will greatly increase running efficiencies of the website and turn complex chores to those that can be managed by a computer semi-literate individual.

    Security Access Control

    This is an important aspect/feature that will be implemented within the web portal. By implementing this, we will ensure that the portal’s administrative intranet is only accessed by authorized users.
    1. Authentication: is the act of determining the identity of a user and of the host that they are using.  The goal of authentication is to first verify that the user, either a person or system, which is attempting to interact with your system is allowed to do so.  The second goal of authentication is to gather information regarding the way that the user is to access the system. Security logs consisting of how, where and when user uses the system will be recorded.

    Note: system will identify users by user id and an encrypted password.

    2. Authorization: is the act of determining the level of access that an authorized user has to behaviour and data.

    Other factors we will consider to ensure security is up help are

    * Connection type.(securely encrypted data on transit and in the database)
    * Update access. (In terms of user rights and in conditions when the more than one persons access the same piece of information thus causing transaction lockig and offer read writes)

    Search Engine Friendly Features to be implemented
    1.    A straight forward sitemap will be developed so that we can have all web crawlers including Google, yahoo, msn can easily go through it.
    2.    As we develop the website we will ensure we follow the w3c standards (World Wide Web Consortium) so that we can ensure that all standard browsers will interoperate and display the revamped website correctly. This is not the case with the current website.
    3.    Blog solution – online journal and comments from different users of on the internet.
    4.    Friend Alert Solution (Email) – To improve traffic on the website we will have “Tell A Friend” script that will enable current visitors forward their friends specific topics of interest.
    5.    Titled Links – Google and other search engines prefer titles that explain content of the pages.
    6.    Need of a weekly update / report which will ensure that Google crawler always visits the website more often. In our case we will have camp reports… Different visitors views, weather, managers’ comments etc.
    7.    Photo Gallery will also be implemented and also customised so that it can become search engine friendly. Ensure ‘alt’ text has keywords that explain the website
    8.    In addition to contact details, application and enquiry forms will be developed so as to make it easy for online clients to reach us.

  • Programming ( Software Developement)
  • We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have  value:

    * Individuals and interactions over processes and tools
    * Working software over comprehensive documentation
    * Customer collaboration over contract negotiation
    * Responding to change over following a plan

    That is, while there is value in the items on the right, we value the items on the left more.

    Some of the principles behind the software development  in us are:

    * Customer satisfaction by rapid, continuous delivery of useful software
    * Working software is delivered frequently (weeks rather than months)
    * Working software is the principal measure of progress
    * Even late changes in requirements are welcomed
    * Close, daily cooperation between business people and developers
    * Face-to-face conversation is the best form of communication (co-location)
    * Projects are built around motivated individuals, who should be trusted
    * Continuous attention to technical excellence and good design
    * Simplicity
    * Self-organizing teams
    * Regular adaptation to changing circumstances

  • System Annalysis

Why and how Requirements of Systems Analysis is necessary.

As a Technolgy based Software service , we are now investing time and resources into effective and streamlined Software Requirements Analysis Processes as a prerequisite to successful projects that align with the client’s business goals and meet the project’s requirement specifications.

Below are what we follow for our requirements in Systems Annalysis.

Steps in the Requirements Analysis Process

I. Fix system boundaries

This initial step helps in identifying how the new application integrates with the business processes, how it fits into the larger picture and what its scope and limitations will be.

II. Identify the customer

In more recent times there has been a focus on identifying who the ‘users’ or ‘customers’ of an application are. Referred to broadly as the ‘stake holders’, these indicate the group or groups of people who will be directly or indirectly impacted by the new application.

By defining in concrete terms who the intended user is, the Requirements Analyst knows in advance where he has to look for answers. The Requirements Elicitation Process should focus on the wish-list of this defined group to arrive at a valid requirements list.
III. Requirements elicitation

Information is gathered from the multiple stakeholders identified. The Requirements Analyst draws out from each of these groups what their requirements from the application are and what they expect the application to accomplish.

Considering the multiple stakeholders involved, the list of requirements gathered in this manner could run into pages. The level of detail of the requirements list is based on the number and size of user groups, the degree of complexity of business processes and the size of the application.

a) Problems faced in Requirements Elicitation

* Ambiguous understanding of processes
* Inconsistency within a single process by multiple users
* Insufficient input from stakeholders
* Conflicting stakeholder interests
* Changes in requirements after project has begun

A Requirements Analyst has to interact closely with multiple work-groups, often with conflicting goals, to arrive at a bona fide requirements list. Strong communication and people skills along with sound programming knowledge are prerequisites for an expert Requirements Analyst.

b) Tools used in Requirements Elicitation

Traditional methods of Requirements Elicitation included stakeholder interviews and focus group studies. Other methods like flowcharting of business processes and the use of existing documentation like user manuals, organizational charts, process models and systems or process specifications, on-site analysis, interviews with end-users, market research and competitor analysis were also used extensively in Requirements Elicitation.

However current research in Software Requirements Analysis Process has thrown up modern tools that are better equipped to handle the complex and multilayered process of Requirements Elicitation. Some of the current Requirements Elicitation tools in use are:

* Prototypes
* Use cases
* Data flow diagrams
* Transition process diagrams
* User interfaces

IV. Requirements Analysis Process

Once all stakeholder requirements have been gathered, a structured analysis of these can be done after modeling the requirements. Some of the Software Requirements Analysis techniques used are requirements animation, automated reasoning, knowledge-based critiquing, consistency checking, analogical and case-based reasoning.

V. Requirements Specification

Requirements, once elicited, modeled and analyzed should be documented in clear, unambiguous terms. A written requirements document is critical so that its circulation is possible among all stakeholders including the client, user-groups, the development and testing teams. Current requirements engineering practices reveal that a well-designed, clearly documented Requirements Specification is vital and serves as a:

* Base for validating the stated requirements and resolving stakeholder conflicts, if any
* Contract between the client and development team
* Basis for systems design for the development team
* Bench-mark for project managers for planning project development lifecycle and goals
* Source for formulating test plans for QA and testing teams
* Resource for requirements management and requirements tracing
* Basis for evolving requirements over the project life span

Software requirements specification involves scoping the requirements so that it meets the customer’s vision. It is the result of collaboration between the end-user who is often not a technical expert, and a Technical/Systems Analyst, who is likely to approach the situation in technical terms.

The software requirements specification is a document that lists out stakeholders’ needs and communicates these to the technical community that will design and build the system. The challenge of a well-written requirements specification is to clearly communicate to both these groups and all the sub-groups within.

To overcome this, Requirements Specifications may be documented separately as

* User Requirements - written in clear, precise language with plain text and use cases, for the benefit of the customer and end-user
* System Requirements - expressed as a programming or mathematical model, addressing the Application Development Team and QA and Testing Team.

Requirements Specification serves as a starting point for software, hardware and database design. It describes the function (Functional and Non-Functional specifications) of the system, performance of the system and the operational and user-interface constraints that will govern system development.
VI. Requirements Management

Requirements Management is the comprehensive process that includes all aspects of software requirements analysis and additionally ensures verification, validation and traceability of requirements. Effective requirements management practices guarantee that all system requirements are stated unambiguously, that omissions and errors are corrected and that evolving specifications can be incorporated later in the project lifecycle.

Outsourcing Software Requirements Analysis Process from Techwebreality

Techwebreality Software Requirements Analysis Process effectively captures user-centric requirements with prototypes and use cases. Our Requirements Analysis Team applies best practices, tools, and methodologies for modeling and analyzing the requirements gathered and then map these to software capabilities for developing superior solutions.

Contact  Us at Techwebreality here for outsourcing your Software Requirements Analysis Process in kenya. We offer comprehensive and in-depth Requirements Analysis by capturing use-case driven requirements which establish requirements traceability and translate into system designs that are aligned with your business objectives and goals.