INFORMATION STRATEGIC PLANNING

It is a process of conducting full-fledged strategic planning in the information domain. It is very beneficial from small firms to enterprises and from enterprises to multinational companies.

  • INITIATE INFORMATION STRATEGY PLANNING PROJECT: First we will gather all the required or eligible persons of our organization in form of a board meeting, jam session, or a routing group discussion. At that place, while maintaining confidentiality we will conduct the other upcoming steps.
  • IDENTIFY YOUR BUSINESS POSITION: Analyzing our available data which will help us a lot in finding our current business position like what we can afford, we can go to how much extent on a particular topic, do we have competitors, what should we do to get more customers, etc.
  • EXAMINE CAPABILITIES & TECHNOLOGIES: First, examine our capabilities and technology so that we can get an idea of what we are eligible to do. Generally, it requires technical experts from different areas so that they will examine and suggest new and better options for our technology and other human-resource-related suggestions.
  • DEVELOP SYSTEM & TECHNOLOGY ROADMAP: Now we gonna develop a new or updated system and technology roadmap as suggested by the technical experts so that it will help us more in dealing with future planning. It is necessary to develop all of the solutions and future strategies too on this roadmap because if don’t do so it may cause a serious difference in planning and implementation.
  • PRIORITISE SOLUTION: The solutions which we have framed based on our system & technological roadmap are now needed to get prioritized based on the current business scenario and consulting with all concerned authorities of our organization.
  • IMPLEMENTATION: Finally it’s time to implement the updated or new information strategy plan with the help of executives and managers or directors of concerning departments of our organization.

Comments

Post a Comment

Popular posts from this blog

DESIGN PRINCIPLES

PROBLEM PARTITIONING: Divide the problem and conquer the problem it means to divide the problem into smaller pieces so that each can be captured separately. ABSTRACTION: The process of hiding certain details and showing only essential information to the user. MODULARITY: It specifies the division of software into separate modules which are differently named, addressed, and integrated later on in to obtain completely functional software. STRATEGY OF DESIGN: To design a system, there are two possible approaches- Top-Down Approach: main components and then sub-components designed Bottom-Up Approach: sub-components and then integrate them to obtain the main component.
Read more

COMPONENT ASSEMBLY MODEL

This model follows an object-oriented methodology where the whole system is divided into components, if they are already available in the library then we import them else we have to build them and at last, we construct the system by integrating them. CHARACTERISTICS: Use of object-oriented technology. Component-class that encapsulates both data and algorithm. Component delivered to be reusable. Paradigm similar to spiral model, but engineering activity involves components. The system is produced by assembling the correct components. ADVANTAGES: Time and resource conservative. Having object-oriented methodology. Components are built once and then they can be reused further. Suitable for small to large object-oriented projects. Very low cost in the construction of the system. DISADVANTAGES: Can’t use it for pioneering projects. Needs good planning and design. Needs a clear and complete definition of the whole system before dividing it into components. Need experts to divide the syst...
Read more

SOFTWARE TESTING

Image
It is a process of verifying and validating that software or application is bug-free, meets the technical requirements as guided by its design and development, and meets the user requirements effectively and efficiently with handling all the exceptional and boundary cases. SOFTWARE TESTING STRATEGIES VERIFICATION: It refers to the set of tasks that ensure that software correctly implements a specific function. VALIDATION: It refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. Verification -> “Are we building the product right?” Validation -> “Are we building the right product?” TYPES OF SOFTWARE TESTING MANUAL TESTING: Manual testing includes testing software manually which means without using any automated tool or any script. The tester takes over the role of an end-user and tests the software to identify any unexpected behavior or bug. There are different stages for manual testing suc...
Read more