Pages

Monday, September 3, 2012

Soft skills part 3

In Information Technology (IT) industry, people always work in teams. The team is a small unit organized to achieve a goal. For example, a software team is organized to achieve a goal of develop a software product; An Information Technology team is formed to achieve a goal of transfer data storage to a cloud computing service provider. Teamwork skill is defined as the ability to work effectively as part of a team to achieve a common goal.

The goal is the reason to organize the team. Without a clear reason, no one would understand why they need to work together. No one would know about their roles or responsibilities or what they are doing in a team. Teamwork requires the sharing of information as members are working with each other. Every team has members with various skills and some have more experiences, some have less. Teamwork is where they learn from each other. Team members must understand their assigned roles so that they appreciate the efforts put in by everyone. This is important as without clear roles and responsibilities, when things do not work well, members often blame others. This is the reason why the roles of project manager and team leader are important. A team leader’s job is to provide the leadership to the team and assign works to members according to their skills and experiences.

One of the most important factors in teamwork is effective communication. Today, most IT projects are distributed in several countries or having team members come from different countries. Having a common language such as English is important. Many IT students do not understand the language requirements and do not consider learning another language is important. According to a recent industry study, if IT workers do have a second language such as English, their chance of getting a good job can be reduced by 75%[I think it can be increased by 75%, may be it is a typing mistake ]. Communicating effectively means that information is shared among all team members. It also means all members must participate in team discussion and technical reviews so everybody can be informed of what others are doing.

According to a teamwork theory, most teams often go through four stages before they can function well. The first is the “Forming stage” when the team comes together and begins to know each other. Each member is often carefully to avoid any conflict but they have not trust each other. Work is slow since members want to defense their views and not say much. It usually takes few days to few weeks to move to the next stage, depending on the size of the team. The second-stage is the “Storming stage” when conflicts breaks out. Team members begin to argue and form subgroups, each with their own view on how to do the work. They do not want to share anything and often avoid each other. It could last few weeks to few months as each subgroup is holding on to its own idea and only share with members who share the same view. Most IT people call this stage “The cold war” as distrust is the rule. Slowly, through fatigue and despair, each subgroup begins to realize that they cannot work toward the goal as sharing of information is essential. The third-stage is the “Norming stage” in which team members begin to cooperate and compromise with each other. The effectiveness of the team begins to improve as team members contribute and discuss more openly. Finally the team enters the four-stage or “Performing stage” when trust is built among members as they recognize their roles, responsibilities and the sum of their individual efforts in achieving the common goal.

By understand the principle theory; a good team leader could shorten the time it takes to develop an effective team. I often advise team leaders to have more team meetings at the beginning of the project to allow members to talk with each other and share information. Experienced manager will watch the team to understand what stage they are in. If the team is in “Cold War” for more than a week, manager should interfere by having frequent meetings to have members to share their views and emphasize on their roles and responsibilities. Teamwork development often takes several weeks to reach the performing stage, depending on the skills and experienced of team members and the talent of the team leader. I often remind students: “If you work together, you will finish faster.”

Teamwork is often a weakness of Asian students when they go to school in the U.S. because their tradition education systems promote individual work instead of teamwork. Many Asian students do not get along with other members. They want to be the “only one” who does the work rather than sharing information with their teams. Some prefer to do thing on what they want instead of following the team process. Global companies also told me that they have difficulty when operate in Asia as their workers often have conflict with others when working in team.

As a team member, you need to understand that everyone on the team is depending on others to get their works done. You have an assigned role and responsibility within the team and it is essential to follow the team rules to make sure that you will function well within the team. Teamwork should be encouraged early in college where students are still developing their skills.

Since teamwork is required in the industry, some students often write on their resume certain phrases such as “Ability to work in a team” or “participate in teamwork” as one of their strengths. But in fact they never work in team and only learn about it in books or articles. This is dangerous because during the interview, there will be questions on teamwork and without participate in team or have real experience, many applicants cannot answer. If interviewers believe that applicants are not honest than what would be the chance to get hired? Please remember that talking about teamwork is easy but it is not good unless you practice it.
Prof John Vu    
Carnegie Mellon University
Original source:http://www.segvn.org/forum/mvnforum/viewthread_thread,1409

Soft skill part 2

Presentation skill is an important soft-skill that college students need to learn. This skill requires students to communicate their thought and ideas on a particular subject, to a group of people. Students need to develop this skill throughout their years in college so when they go to job interviews or work in the industry, they will not feel uncomfortable. Presentation skill is not difficult to learn but it requires a lot of practices to be effective.

The most important thing for a presentation is to prepare as early as possible. Do not wait until the last minutes because you need to gather all information to prepare for it. Typically a presentation has an introduction, the main topic with key points that you want the audiences to know, and a conclusion. Your goal is to make the audiences understand what you want them to know before you get to the conclusion. How much detail your presentation is will depend upon the time you have to speak. For most students, my advice is to keep the presentation to no more than fifteen minutes. Even when you work in the industry, you may not have to present longer than that, unless you get to position levels of senior manager or executive. However, you need to know that any presentation of more than an hour will make audiences lose interest, as few people can keep their attention that long. After the conclusion, you may want to ask the audiences if they have any question on what you have said. Sometimes, the discussion afterward between speaker and audience is more interesting than the presentation.
Many people believe presentation skill as difficult and require a lot of trainings. The fact is it may only apply to public speaker or politician, but as students and future engineer, you do not need a lot of trainings. Most of what you present is probably technical things that you already know so all you need is practice to gain confidence.

There are many presentation techniques, each person may find certain technique more useful but there are two things that you must avoid: Never read from a prepared written speech and never read the slide. The audiences have limited attention and do not like someone to read a speech. Reading from a written speech means you are not prepared and have to rely on something. By doing that, you give the audience the impression that maybe someone else is preparing it for you instead. I always advise students to have a short outline with few key points written on a small piece of paper to remind them, just in case they forget. The rule is no technical presentation should be written as a speech. You do not want to “lecture” the audiences but “converse” with them because lecture or speech is boring where conversation is interesting.

Today, people often give presentation using multimedia equipment and PowerPoint and some read from the slide. The fact is audiences can read the slide faster than you can read. They will lose attention if you just read the slide to them. My advice is you should avoid given presentation by reading from a prepared written speech or read slides with a lot of text. It is better to keep it simple by given presentation just like you talk to a friend to helps the audience focus on what you say instead of something else.

A presentation should be organized to lead the audience from the beginning to the end. It is like telling a story, you must start with general things then narrow down to each important point in detail until the audience understands what you want them to know. It is also important to add example for each key points to illustrate why it is important. Just like a Work Breakdown Structure (WBS) in designing software product, you should break the presentation into several key points so if needed, you can add, delete or change the details without much effort.

A good speaker is flexible to adapt to the time constraints. Sometime you may talk fast when under pressure and sometime you may talk slow when stumble into something that you are not prepared. That is why practice is important. The best is practice it loud in front of a mirror and measure the time so you know how long it is. Prepare an extra example or short story in case you have extra time. Similarly, you should put the most important point first so that if you run out of time, the audience still has the most important things. You must practice your presentation until you feel prepared. You should practice the entire presentation, including the use of slide and multimedia equipment that you will be using. The best way is giving the entire presentation to a few friends and asks them for feedbacks. This will help you identify any problems so you can adjust and make it a successful presentation.

I often advise students to start the presentation with a question because question will get audience attention. For example: “Why do you think we should use open source in this project?” you can follow it with an explanation then proceed to your detail key points. At the end of the presentation, you should summarize your key points to ensure your audience will remember them. During the presentation, audience may have questions. Some questions can create confusion to any presenter, so the best way is try to anticipate any questions that your audience may have during and after your presentation. Think about the audience that you will present to and think of anything in your presentation they may not know so you can add an example to make it easier to understand. If possible, identify information not addressed during your presentation that the audience may ask. Prepare responses that can be used to quickly answer any questions that may arise. Having answers ready is the key to demonstrating your expertise on the presentation topic.

Technical presentation is not difficult. It is really an explanation or sharing information to an audience. To succeed, you must gather all the facts and data to validate your points and support your conclusion. The most important is to practice it throughout the time when you are still in school to gain confidence. When you are confident and well prepared, I will have the presentation skills that you need.
Prof John Vu     
Carnegie Mellon University
Original source:http://www.segvn.org/forum/mvnforum/viewthread_thread,1408

Sunday, September 2, 2012

Soft-skills part 1

Many students ask me about Soft-skills and where can they learn these skill? Basically, Soft-skills are skills that determine a person's ability to “fit-in” and excel in a particular environment such as a company or a project team.

There are a lot of “Hypes” about soft-skills but in fact they are mostly common sense. There is a book called “How to Win Friends and Influence People" by Dale Carnegie, published in 1936. This book has been translated into many languages and I recommend that students read it, not one time but many times. I read this book when I was in high school and I am still reading it today. If you can apply most things that this book mentioned, you have all the “soft-skills” that you need to succeed in life.

There are schools, classes, seminars that teach Soft-skills. Many are designed to train professional people but as students, you should develop your soft-skills when you are still in school because you need them after graduate. The list of soft-skills can be long but college students need to develop at least five essential skills: Communication, Presentation, Teamwork, Conflict resolution and Leadership.
Communication is the dialogue that occurs between two or more persons. The skill is the ability to speak in a clear manner so that other people will understand. Students often asked me: “I talk to my friends all the time, why do I need this skill?” My answer is “Communication is knowing when to talk and when to listen.” Some students talk a lot but never listen. Some students do not think before they talk, they just make a lot of noise. These students do not have communication skill.

Listening is the most important skill of communication processes. Students must learn how to listen attentively and avoid disruption when other is talking. This skill is difficult to develop because it must be part of your character. Being a good listener means you must have patience and empathy. You must have an open mind and a desire to understand others.

Speaking is an important skill. Good speakers always think before they speak. They speak clearly and get to the main point quickly so listeners can respond. Many students believe to be good speaker, they must use fancy words. On the contrary, good speakers always use simple words to get their views easy to understand. Students need to know that wrong words can hurt somebody or create a negative image of the speaker. Good speakers choose their words carefully to create a positive language; their message is always polite, pleasant, and practical to create an impressive positive impact on the listeners. Students must learn to avoid using technical terms in daily conversation. For example, IT students often use technical terms without knowing that the listener may not understand it. The term “Back-box testing” is common among testers. The term “Unit test” is common between tester and developers but others may not understand. It is important to know this and avoid using technical terms in your daily communication. Some students use text messages with short word and it becomes a habit in their conversation with friends. When they go to job interview or working in the industry, these terms are not acceptable because it implies an attitude of disrespect.

There is another important communication skill called “non-verbal communication” or the expression of body language such as facial expressions, eye contact, and gestures which are also part of the communication process. According to a study about communication, Professor A. Mehrabian found that 55% of meaning in a conversation comes from facial and body language and only 38% come from vocal inflection.

To westerner, during the conversation, you must look into each other and have eye contact. If you look down or avoid eye contact, it is a symbol of weakness or not honest. On the contrary, most Asian cultures consider look straight into somebody face and eyes contact is a symbol of disrespect and challenging. You must understand this difference and act accordingly. When people communicate and standing, the position is also important. Most Asians do not like to talk when standing unless for short conversation. Westerners do carry serious conversation when standing and the position of your feet is important. If you are standing with their feet very widely apart, then it shows that you are very aggressive and want to dominate the conversation. If you are standing with both feet almost tied together it means you are weak, submissive and afraid. The best position is stand with your feet have the same width with your shoulder. Asian culture does not pay attention to these details but western culture considers body language important and they often judge you on your posture.

Effectively communication means choosing the right words, delivery them in a positive manner and correct body language. A recent industry research on job applicants found that for every hundred candidates, only fifteen are hired. The other eighty five candidates are not selected because they do not have proper communication skills. All candidates have technical skills and qualification and they are selected from the list of thousand applications for interviews. They do not impress the hiring managers because their poor communication skills. The research revealed that 30% of them come unprepared to answer questions not related to their field of study; many have no idea about technological trends or what is happening in the world. It is an indication that they do not have the broad knowledge to function well in the industry. 67% do not speak clearly or answer questions properly; many are nervous and not confident of themselves. 58% have improper body languages and incorrect gestures during the conversation, such as not maintain eyes contact, scratching excessively, do not sit erect but slouching in the chair. The research concludes that most students have good technical skills but are not able to express themselves correctly. Some speak fluently, but cannot listen well. Many have problems with their expression and body language or use inappropriate gestures.

Beside speaking and listening, reading, writing and group communication are also part of communication skills. Most colleges require students to read a lot. Without a good reading skill students will struggle when they enter college and often overwhelm by the amount of reading materials. I have found that reading and writing help improve speaking and listening. Most good readers are usually good speakers because they have a vast amount of knowledge that they can use. I always advise students to improve their communication skills by give sufficient time to reading. They should read on a daily basis so that their memory gets refreshed with the knowledge. Many IT students believe that they only have to read technical books. That is a mistake. They should read whatever they like and make reading a key activity in their lives. Reading opens the mind to many things when they read news, magazines, blogs, and articles of their interest to update their knowledge. They should also read history, world news, economic and business news, to keep themselves updated with current events.

Group Discussion is about communicating with a group of people. In a group discussion, people are brought together to express their opinion and exchange of views on a subject. In group discussion students learn about group dynamic, content collection and leadership attributes. In college class discussion, professors judge students on who are well prepared, who have better speaking skill and who have the leadership skills. Students must learn to speak clearly and politely to the group. They need to know that this is a discussion not an argument and control their thought to stay with the discussion topic not to speak irrelevant information. They should also control their emotion and avoid unnecessary gestures.

Communication skills are essential for getting good job in the industry. Students should develop their communication skills when they are still in school by participating in class discussion; learn to choose their words carefully to create an impressive impact on the listeners. They should develop good reading habit to enrich their vocabulary, expand their knowledge beyond technical area to understand the changing world that they are living in.
Prof John Vu     
Carnegie Mellon University
Original source: http://www.segvn.org/forum/mvnforum/viewthread_thread,1407

Software project management

A project vision is the direction of the project. It is the “Compass” that guides project team to move forward to the same direction. The vision must be communicated to team members at the beginning of the project to give the team a view about the project and how they must work together to achieve that vision.

Some project managers issue the vision to the team then move on to other activities. In that case, the team may lose sight of the vision because they are always busy with their own works. Good project managers will not letting anything distract them from the vision because if they become distracted, the project may not be successful as expected. Team members work best when they have all the information they need to do their tasks but they also need information about how their tasks fit into the vision of the project. Being able to put their tasks into a bigger context provides motivation and helps members make better decisions.

Some managers do not know how to plan projects or create vision. They do not even know how the project should be done so they do not want to share their plans with anyone. They feel insecure about their positions so they often hide behind “Busy works” and avoid talking with team members. When team member asks, they always find excuse that they are so busy and do not have time. The most used excuse is “Having to go to meetings with other managers” so attending meetings become their daily work. These managers do not trust their teams but consider them as “subordinates” rather than people who are capable of doing the work. When people lack a vision or information, they fill in the gaps with their own beliefs and sometime rumors. Rumor gives misinformation and often consumes a lot of time to correct it.

Project managers need to know about status or progress of the project so they can report to higher managers. Without a vision or project plan to monitor against, many rely on individual meetings where each member reports to them instead of team meetings. In this case, members only provide a fraction of the information a manager needs to know. Many important issues remain hidden in this status meeting. For example, team member may be reluctant to admit that they have problems, or facing difficulties, or talk about the information that a project manager needs to know. Without a clear picture of the project, these managers cannot make good decision. Sometime, they do not want to report bad status so they let things happen and when it is getting worst, they blame their own people.

A good project manager always monitors activities to ensure that every action is done to achieve the vision. He collects and evaluates data on schedule and budget to identify risks and respond to them quickly. He has weekly meeting with the team to share progress and keep everyone focus on their assigned tasks. He knows that software projects often have problems; team members always face obstacles such as dealing with changes; not having enough time for tasks etc. Therefore, he must eliminate any distractions to keep the team focus on what they do.

Good project manager does not work alone but always involve the team into project activities. At the beginning of the project, he brings the team together to discuss the objectives of the project. He asks team members for their opinions to get the best suggestions. By engage the team early; he creates a sense of teamwork that allows members to feel that their suggestions are important. When team members feel they are important, they work hard to achieve the vision which lead them to overcome obstacles and strives for success.

Some project managers consider themselves as “Bosses” and project management is about giving orders. This is a mistake. When they order team member to do something, they are not giving the person the opportunity to think about what to do or how to do it. In this case, team member is limited to do exactly as manager tell them to. They will develop habit of only wait for instruction and become reactive instead of active. They cannot analyze tasks or learn anything new and that is why many projects are late. They are late because team members are waiting for managers tell them what to do and without the direction, nothing will happen. A good manager does not give orders but instructions. Giving instructions is not telling somebody what to do, but telling them exactly what he wants to be done. In this case, team member must think on how to do it. Rather than mechanically just doing a task, team member will have to think about the process, the procedure and all the details on how to do it. In this case, they must learn to think and be more active in improving their skills. Good team members always think when they are given an instruction. They always identify different ways of doing the task and consider which way is better. When team members come up with their solution, they feel good. It encourages them to learn more and it improves their confidence in what they do. If something happen to their work, they will be confident to defend it themselves. Giving instructions is the best solution that works well for most software developers.
Prof John Vu     
Carnegie Mellon University
Original source:  http://www.segvn.org/forum/mvnforum/viewthread_thread,1414

Early Project work

Even today the numbers of software projects failure are still high. Somehow software managers continue to rush into projects without even thinking why past projects failed. According to an industry research, a majority of project managers do not receive adequate trainings or know how to plan a project. Many project managers confused a project plan with a project schedule. A schedule is only a small part of a project plan; it usually takes the form of tasks complete within a timeline. The project plan is a roadmap providing guidance on the priority of activities, the scope of work, the life cycle, the method and tools to be used. It identifies customers, users, business strategy, quality, risks, and how project costs and people will be managed.

Most projects fail due to bad requirements. This is the number one issue that causes scope change, which leads to more time and budget necessary to complete the project. That is why the job of requirements engineer or business analyst is important but few companies have these roles and few schools teaching this skills. Many companies expect that project manager should be responsible for project requirements and this is a big mistake. Requirements and customer relationships require a different skills and a lot of efforts and a busy project manager cannot adequately manage the project and the customers at the same time. This is also where some management textbooks failed to address. Bad requirements or poorly defined requirements will lead to a bad project plan. Since the project plan reflects the work, the resources, the budget, and time necessary to satisfy requirements, it is easy to see the importance of getting the right requirements and the project.

A requirements engineer is trained to work with customers and ensure agreement from all customers before project planning. A requirements engineer work with customers to collect their needs, understand their problems and document them in a requirements specification. Customers must review the requirements documents and approve before the planning phase of the project. Requirements engineer work with project manager to translate these requirements into the project scope statement, as well as the major components that will satisfy the scope. There are several essential elements that need to be included in the project definition:
• A description of the business problem and the solution to that problem
• A description of the benefits of the project (the business case)
• A definition of the project vision, goals, scope and budget
• A list of the major deliverables which, when delivered to customers will completely satisfy the requirements of the project)
• Project committed delivery dates

The project definition is the first part of project planning where the project team will be involved to breakdown these requirements into smaller components. The Work Breakdown Structure (WBS) is the foundation of the project plan. It is a hierarchical logical structure that represents all the work necessary to produce all the project deliverables.

By spending more efforts in the beginning, the project can avoid unnecessary requirements changes and project managers can organize the project to better chance of success.
Prof John Vu    Carnegie Mellon University
Original source:

Software development process

Many students are well trained in coding because a majority of their time in university is focusing on coding but little on software development process. Some students consider software development is an individual work as they often receive individual assignments that each must do and most assignments are about writing code. When they go to work, many have a tendency to start coding immediately after receive an assignment without fully understand the problem. As requirements often change and they have to modify their code, they often make mistakes that need fixing. The more they are fixed, the more complex their code becomes. Eventually, it will be too difficult to understand the structure of their code and their logic for testing or maintaining. If developers just code and fix and do whatever they want then it would be difficult to integrate their codes into a cohesive software product.

When students are trained on software development process, they understand that development is not just writing code and it is a team effort. Before starting, the team must have common understanding of the problems that they must solve, the project goals, the project activities where each team member has certain roles and responsibilities for the work. The software process is a roadmap that shows the team how to develop software from the high level to the detail level. There is a sequence order called the development life cycle where the entire process is dividing into several phases and each has certain roles, responsibilities for team members.

The software process starts with the understanding of the problem by verify the requirements with customers. Because customers often do not describe their needs clearly and often change their minds, the team must make sure what customers have asked for is what they needs. Only when these requirements are discussed and confirmed, the team begins to document them into the software requirements specification. By following the process, the team understands that the most common cause of project failure is unstable or poorly defined requirements and by having the requirements fully validated they can reduce the risk of changing requirements. After having customers approved the requirements document, the team starts their own discussion to make sure that every team member understands the problem well enough before they divide the project into smaller tasks that they must do.

By following the software process, the team defines the architect of the system with several components. Team members identify the interfaces between these components and then verify that all components can be traced back to the requirements so that the product will meet customer’s needs. This is important because any error in architecture can create issues during software integration in later phase. When a project moves from requirements phase to architecture phase, the team will discover that there are many “Derived requirements” that need to be done. Sometime the list of derived requirements is much more than the original requirements because an architect must consider things such as performance, scalability, usability, and maintainability that customers expect but do not ask for. Based on the architecture, the team selects software tools that they will use to build the system. At the same time, team members can begin to create a set of unit tests to be applied once they finish their code. Many developers do not think about testing until they finish coding but if they start to develop unit tests early during architecture phase, they can avoid many mistakes that often happen during design phase. By working on unit tests early, they understand the requirements better that help them to design the product better.

Design phase is where the internal logic of each component is organized. During this phase, team members work on the details of the data structures and the algorithmic of each component. In architect phase, the main focus is on identifying the components and the relationship of these components and how they interact with each others. During the design phase, the focus is on designing the logic for each of the components. Team members follow a process and using a set of techniques and guidelines such as problem partitioning and abstraction. The use of abstraction allows team members to focus one task at a time, without worrying about the details of other tasks. When all tasks are done, the team should follow a verification process by having a review of the design of each component. Typically, the project manager, the system architect, and the quality assurance must participate in the review to make sure that all works are done according to the plan, the overall system architect, and in compliance with the standard process.

When a design is fully verified and approved. Team members can start the implementation phase (Coding). Many people like to write code right away but if they follow the process, they must select data structure that meets the needs of the design; keep the logic structure as simple as possible; select meaningful variable names consistent with the standards. By select data structure first, then start with a logical organization of the coding structure they can avoid a lot of mistake often happen during this phase. After complete the first coding, team member must conduct a code walk through to review their code to make sure they follow the coding standard and their structures are consistent with the way the project is organized and planned. Each team member must perform unit tests and correct uncovered errors before move to the next phase.

In the testing phase, team members transfer their code to the testing team. Testing is the process of executing a program with the intent of finding error. A good test is one that has a high probability of finding error. By following the process, team members understand that tests should be planed early during architecture phase and all tests should be traceable to customer requirements. Testing should start in the smallest part and progress toward testing in the larger part and eventually the entire software product. (Unit test, Function test, Integration test, System test etc.)
Prof John Vu    Carnegie Mellon University
Original source: http://www.segvn.org/forum/mvnforum/viewthread_thread,1461

Systemic software development

A software developer wrote to me: “We had several project failures. Customers were angry but the project manager told us that they were customer’s faults because they kept changing requirements. We are starting a new project but I am afraid that we will make the same mistake again. What can we do to avoid this problem? Please advice.”

Answer: If the customers keep changing requirements then you need to have a requirements engineer or business analyst to spend time with customers to obtain better requirements. This is an important role in software development but many companies do not pay attention. If the requirements are wrong than everything will be wrong no matter how good you can design or code. If your company does not have someone to do this then they should hire people who could do that job. When a project fails, your manager should not blame the customers but should identify the cause and fix it so it will not happen again. When customers are not happy then it is bad business. No company can survive if their customers are not happy. When a project is late, it takes more time, more money, and more efforts than previously planned. It means the company has to pay for these extra works and it means losing more money.

Changing requirements is a common problem in software industry. It is usually due to the lack of knowledge on software requirements. Many project managers think that they understand what the customers need and proceed to development without any customer validation. Many developers presume that they know all the features customers need then start design and code without any customer review. Progress is measured by each line of code built throughout the process until requirements begin to change. Fixing software after building is costly and time consuming. It often causes huge effort waste with hundreds of hours unproductive and hundred lines of code changes. This is why you need someone who understands requirements to work closely with customers to get the right requirements so you do not make the same mistake again.

There are different views of requirements. A manager’s view of requirements is often a high-level concept of a product or a business problem that must be solved. A user’s view of requirements is mostly the functions, the interface, and the navigation of screens. If the requirements are mostly functional, the project team may not understand various information hidden under the view of functionality. As a result, customer’s expectations may not be achieved.

To avoid this issue, project team must understand several views of requirements. The highest level view is the business requirements, representing the objectives of the customer. This is really the vision and the scope of your project. The second level view is the user’s requirements, which describe all the tasks that users must do when using the software. These are best captured in the form of use cases, which are scenarios of typical interactions between the user and the system. This is the architecture of the system with hardware, software interface and the navigation of screens. However, use cases alone do not provide enough detail for developers to know what to build. Therefore, you need the third level view or the functional view which derive from the use cases. The functional requirements clearly define specific things the software must do. This is the design of the system with each function clearly identified. However, there is another view called the non-functional view or the quality attributes which does not come from customer but from developers that deals with the quality of the software such as performance, efficiency, usability, or scalability etc.

By understand different views, developers can organize their work systematically to meet customers’ expectation and develop better software product.
Prof John Vu    Carnegie Mellon University
Original source:http://www.segvn.org/forum/mvnforum/viewthread_thread,1602