Chapter 8 - Starting the Solution by Harvinder Singh


  Chapter 8
Starting the Solution

We are transferring from an abstract global to the physical international, from policy to technology, from problem to solution; from purpose to design: we have reached the closing quadrant of the Brown Cow Model, in which will be determined how we are going to enforce the essential business. With a solid know-how of the essence of the business, which means that the real trouble to be solved, it’s time to determine which components of that problem would advantage from being automated. The commercial enterprise analyst juggles many factors to determine the most appropriate product to build.

Iterative Development
Iterative development is a way of breaking down the software improvement of a large application into smaller chunks. In iterative development, feature code is designed, developed and examined in repeated cycles. With each iteration, additional functions may be designed, advanced and examined till there is a completely useful software program application prepared to be deployed to customers. In any event, it is usually more efficient to begin the discovery of need with abstract models and conversations instead of concrete implementations. No matter how you are developing software, the critical part of this process is the discovery, by both you and your stakeholders, of the real needs of the solution.

Designing the User Experience:
Designing the whole of the user experience is the best way to come up with a product that makes people want to buy it and/or use it. Experience design is a significant topic and one that we consider to be beyond the scope of this book. However, we briefly mention it here because this kind of design is beginning to play a larger part in our development activities. Experience design aims to produce a usage experience that is pleasing and exciting, as well as relevant to the culture and aspirations of the user. Such design focuses much more on how the product makes the user feel than on adding functionality to the product.

Innovation:
Innovation, as we use the term here, means thinking differently about the problem to find a new and better way to do the work, or in some cases to find better work to do. Instead of rushing ahead with the first-to-mind solution or the obvious solution, we urge you to spend just a little time with fellow business analysts and other stakeholders to come up with something better, something that will be longer lasting and more appealing, something innovative.

Essential Business
Before starting on a solution, we will have to collect a good chunk of the functional needs and a significant portion of the non-functional needs for the work that you have been studying. The purposeful needs can be supplied to you in the form of an enterprise use case (BUC) scenario, a group of atomic functional requirements, or properly crafted consumer stories. The non-purposeful requirements ought to be taken under consideration while making selections about the solution.

Consider the Users
Whatever it is that you intend to build, someone has to use it. If you want to sell your solution, or if you need people to start using it voluntarily, then it stands to reason that you will want to make the product attractive to its intended audience. You know the functionality, but now you have to make it fit seamlessly into the users’ expectations, or their perceptions of how it should behave. Of course, you cannot design something that will satisfy people if you don’t know those people or understand how they behave.
Personas are used when you have a large number of in-house users, or a large number of customers who will be using the product. Personas are constructed from data collected through surveys of your target audience and so represent most of your eventual users. We urge you to use both observations of real users, or personas. Whatever you do, you must construct a product that is appropriate and well matched to almost all of your users.

Comments

  1. Chelsia Palta19 April 2020 at 01:34

    Thanks for providing this useful information. In addition, the Iterative Development is Typically used in conjunction with incremental development in which a  longer software development cycle is split into smaller segments that build upon each other. Iterative and incremental development are key practices in Agile development methodologies. In Agile methodologies, the shorter development cycle, referred to as an iteration or sprint, is time-boxed. At the end of the iteration, working code is expected that can be demonstrated for a customer. Iterative development contrasts with a traditional waterfall method in which each phase of the software development life cycle is “gated.” Coding doesn’t begin until design of the entire software application is complete and has gone through a phase gate review. Likewise, testing doesn’t begin until coding is complete and has passed necessary phase gate reviews.

    ReplyDelete
  2. Paramjeet Kaur Toor20 April 2020 at 18:53

    Good information about why it is important to consider the users. As we get that we must know our users and we should know how they will react or behave to our product. In order to know more about customers, we can study about ethnography that involves the study of custom people and their culture. By doing this, we will be understand the nature of any specific target group like how they think and how they behave. For example, for making Scotia Pay successful, we must know which age group is going to use it most and are they familiar with technology? as these things help to make product more successful.

    ReplyDelete
  3. Liliane Marino21 April 2020 at 15:37

    Thanks for the information. I would like to reinforce how important is to document the design decisions. During the design phase, you make important decisions and part of your responsibility is to document them – the reasons why the resultant system is as it is. Important to mention that you are also responsible for leaving behind documentation for the future generations who will maintain your solution.

    ReplyDelete
  4. Hassan Kamara23 April 2020 at 19:45

    This information is very good, you explained some for the process of finding a solution very well. I do wish that the designing of the user experience was explained more in depth in the book but i found the innovation section of this blog post to be interesting because you would think if the goal was to start to try to find a solution that the first thing to do is come up with solutions, but with innovations you gather fellow BA's and other stakeholders and dive deeper into finding a more in depth and longer lasting solution compared to just finding a solution quickly.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 4: Elicitation and Collaboration

Image
posted by Liliane Castano Marino According to chapter 4 of the BABOK,   t he Elicitation and Collaboration knowledge area describes the work of business analysts to understand stakeholder needs, concerns and the environments in which they work or operate.   In this area of knowledge, the business analysts extracts the information necessary to assertively understand the change and what really needs to be done.   It is an ongoing work as long as business analysis work is occurring. The Elicitation and Collaboration knowledge area is composed of the following tasks: 1)        Prepare for Elicitation At this point, it is important to establish what information will be needed, which stakeholders will be involved, which work products will be produced and which techniques will be most appropriated to reach the required results. The professional who does business analysis needs to go far beyond interviews and questionnaires. BABOK points...
Read more

Chapter 6 - Scenarios - posted by Harvinder Singh

Image
Chapter 6 - Scenarios At this stage of the requirements process, the business events were identified, and thereby the business use cases (BUCs) that respond to the events. The scenarios must be used to model and record the BUCs, as they are very effective, largely because of their ready acceptance by nontechnical stakeholders. Formality Guide Scenarios are useful in most situations, e can understand them, and they fit into any development style, but projects will have different needs related to their size. Let’s have a look on these three projects: ·         Rabbit projects can use scenarios as a trawling technique, discover the required functionality by working with scenarios. Rabbit scenarios usually overlook non-functional requirements and capture them later by writing separate non-functional story cards. ·         Horse projects might consider scenarios as an alternative to writing ato...
Read more

Chapter 3: Business Analyst Planning and Monitoring By, Hassan Kamara

Image
Business Analysis Planning and Monitoring According to chapter 3 of the BABOK, the tasks of business analysis planning and monitoring are presented to coordinate the efforts of stakeholders and BA’s. The 5 main knowledge areas that will be covered are: Ø   Plan business analysis approach Ø   Plan stakeholder engagement Ø   Plan business governance Ø   Plan business analysis information management Ø   And identify business analysis performance improvements 1.       Plan business analysis approach. Plan business analysis approach can be defined to be the planning of business analysis work from selection or creation of a methodology to planning the individual tasks, activities and deliverables. BA’s also identify initial techniques that could be applied. The approach is used to define a method to conduct the business analysis activities. The approach should; align to the goals of he change, coor...
Read more