How to provide reliable project suggestions on modern software engineering Handouts

The internet age is both a great and a bad age for innovators. You have a lot of opportunities to make products that affect the world. However, it seems that any idea has been thought of, made, listed, and transplanted to various platforms... In addition to envy others, what opportunities do we have in the future? However, when students are keen on stealing food and killing the Three Kingdoms, they often come up with new ideas, new technologies, and other people come up with new ideas and business models. we stole a lot of food and spent several nights in Three Kingdoms, but we still don't have the idea...

In the course "modern software engineering", students cannot wear new shoes, take the old path-learn many new technologies, new development models, and new team management methods, but there is nothing new, no one is using it, and the demonstration will be discarded (such as a virtual student management system, library management system ...). We need to create innovative projects.

 

First, "innovation" can be divided into improved innovative incremental innovation-(several features are added to the software, which makes a program faster and migrates the program to a new platform ), and disruptive innovation ). these two types have their own importance and should not be neglected.

 

So how can we propose new ideas and how can we convince others that my ideas are reliable? Some students use the "two-shot" method to solve the problem:

-Shoot your head: Hey, how about making a book auction website?

-Pat chest: No problem. There are a lot of Asp.net books on the market. I can write a shopping website two nights later.

 

It is not enough to pat your head and chest alone. The consequence of "two beats" is often the third shot-beat your ass and leave. some may also suffer from shoot their heads or chest attacks. How can we come up with reliable ideas and persuade others in a systematic manner if we can't pat our head, chest, and ass? Sleeping in the dormitory, gathering, drinking, brainstorming?

 

The following is a relatively systematic framework-NABC model for your reference:

1) N (Need Requirement)

Your idea solves users' needs? This requirement can be clear and open (for example, to be able to play the Three Kingdoms online ). it may be unclear. For example, no one said before: Well, if I can find such a website, I can steal food...

We need to fully understand the user's pain, where they are not satisfied with the existing software and services. However, users often do not know about disruptive innovation. For example, before Henry Ford invented a car, if he went deep into the user and understood their needs, the user would tell him-I want my carriage to be faster!

 

2) A (Approach practices)

Okay, you have found N. What to do next? You have to check what tricks you have, especiallyUnique TacticsTo solve the user's pain. You can't say that I will be C ++, so I can write this software well. You have to have a unique approach, for example, someone's face recognition technology will do very large-scale data processing. What will you (your team) do? Will only bubble sort?

These tactics are not only technical, but also business models, regions, contacts, and industries.

 

3) B (Benefit benefits)

At this time, you have a Unique practice (Unique Approach). What benefits does your product/service bring to customers/users? If a user already has a solution (for example, if the user is already using QQ chat), what are the specific advantages of your product, so that the user can leave the existing product and use your product? There is also a Benefit/Cost (Cost) problem. If you want users to have 4 GB of memory, the best video driver, and 4 M broadband connection to use your "better" video chat tool, how many users are willing to pay this cost?

 

4) C (Competitors competition)

Competitors are not idle. How many competitors are there in this market? Do you know? If you are not the first product to enter a market, can you win?

Let's take a look at the description of First Mover Advantage (FMA) and Second Mover Advantage (SMA.

 

For more information about NABC and related cases, you can read this thick book-

Innovation: The Five Disciplines for Creating What MERs Want

 

For students in the "modern software engineering" Class of HKUST, please post each of your reliable ideas on your blog Based on the NABC framework. Each team member should come up with at least one idea, which is more beneficial.

Update:

After practicing NABC many times, I realized that I should add D: Delivery. How can we deliver your innovative products to users?

Example 1: You think of a good idea to create a better navigation page than hao123! Let's assume that NABC is okay. How can we deliver such a simple product (Deliver) What about users?

Example 2: If you think of a mobile phone application, NABC is good. How can you deliver the product to tens of millions of users?