Model-Based Testing - Testing Experience

More documents

Recommendations

Info

As I evolve in my own area of expertise, I am trying to constantly reinvent small aspects of what I consider best practice. Most recently, to address the incredibly complex requirements of a large client initiative, maybe the combination of Waterfall and Agile approaches and principles should give us the required and superior results. Stakeholders: Project management’s mantra for success is: “Satisfy your Stakeholders”; and once this satisfaction has been granted to the respective stakeholders we can rest assured that the project will be successful and all the requirements will be met. By stakeholders we mean any person who positively or negatively influences the outcome of the project. Examples of stakeholders include: customer, user group, project manager, development team, testers etc. Stakeholders are anyone who is interested in the project. They may also exert influence on the project’s outcome and objectives. The project management team must identify these stakeholders, determine their requirements and expectations and to the extent possible manage their influence in relation to the requirements to ensure that a successful project is delivered. Identification of these stakeholders should begin as early as possible in the project because the earlier the requirements are gathered from these stakeholders, the better it would be for the project in terms of scope, time and cost. Estimation: In project management, accurate estimation is the backbone of sound project planning. Without an estimation, the project will be carrying on infinitely, thus impacting the constraints of the projects, namely scope, time and cost. Many processes have been developed to aid engineers in making accurate estimations, such as analogy based estimation, parametric estimation, Delphi method, function points, and Program Evaluation and Review Technique (PERT). A sound estimate starts with the creation of a WBS (Work Breakdown Structure). A WBS is a list of tasks that – if completed – will produce the final product and deliverable. Once the WBS is created, the team must create an estimate of the effort required to perform each task. The most accurate estimates are those which rely on previous experiences (analogous estimation). Team members should review previous project results and find how long similar tasks in previous projects took to complete. Causes of delays in the past should be taken into account when making current estimates. No estimate is guaranteed to be accurate. There can be various scenarios, e.g., people get sick, leave the organization, teams run into unexpected technical issues and problems, etc. The main objective of estimation is not to predict the future, instead the main objective is to create an honest, well informed opinion of the effort required to perform a particular task. In my opinion, a project manager can help the team create accurate estimates by reducing uncertainties about the project. The most effective and productive way to do this can be: ▪ Creating an accurate and detailed scope document ▪ Reaching a consensus on the tasks that have to be performed ▪ Discussions on assumptions with the entire team Risk management: There are nine knowledge areas in project management, which are: integration, scope, time, cost, quality, risk, communication, HR and procurement. To my view, the most important ones which affect project on a very large scale are: scope, time, cost, risk and quality. I do not wish to under-estimate communication, but if feel that risk management also plays a valuable role in project management. The earlier the risks are identified, the better it is for the project and the team to succeed. Risks can come from any of the following: ▪ Project Failures ▪ Natural causes and disasters ▪ Deliberate attach from adversary ▪ Uncertain financial markets ▪ Other uncertain events Once the risks have been identified, we need to prepare strategies to manage risks. The strategies include: ▪ Transfer risk ▪ Avoid risk ▪ Accept risk ▪ Reducing the negative effect or probability of the risk My experiences in project management activities: From my personal experiences, project management is a wonderful experience.. In my opinion, the most important trait for a project manager has to be TRANSPARENCY. If he/she is open, then other factors (scope management, time management, risk management, cost management, etc.) will automatically fall in place. Other traits that follow transparency can be: project management experience, communication, guidance and mentoring, and motivating the team. The entire team looks to the project manager for motivation and leadership, and if the project manager stands up and delivers, then the entire team will support the project manager which in turn benefits both the project and the organization. Challenges in project management: In my opinion, some of the challenges faced while undertaking project management activities include: ▪ Lack of project management experience ▪ Time, cost, schedule ▪ Resource handling ▪ Conflict handling ▪ Risk handling ▪ Unrealistic deadlines ▪ Communication ▪ Scope changes ▪ Uncertain dependencies ▪ Insufficient team skills ▪ Lack of discipline and accountability 38 The Magazine for Professional Testers www.testingexperience.com
▪ Non-involvement of customers and end-users during the project ▪ Vision and goals not well-defined ▪ Shifting organizational priorities ▪ Change control not well-defined ▪ Geographically dispersed project teams ▪ Using the wrong tool for the job ▪ Spending too much time in project/status meetings And ... not to forget, last but not least – QUALITY! Project leadership is a skill that takes time to develop in a person or organization. Achieving success requires analyzing setbacks and failures in order to improve. Focusing on each project’s challenges and learning from them will help to build a more capable and successful project management capability. Conclusion: Project management activities, in some form or other, have been used for more than 5,000 years, yet there is still more to learn in the continual development of the techniques, practices, and procedures of modern management skills. In the past 50 years or so, the use of project management has grown exponentially, which can only be attributed to the sharing of information. Many books have been published and people are getting trained in project management, but still there are gaps in practice and performance that can only be filled through sharing of personal experiences with project management competence. Sharing is easy when one can mentor or write a short article on project management practice. Internal project electronic bulletin boards may be used to inform the team. If one has something to share, we should find a means to get it to as many people as possible. > biography www.testingexperience.com Santosh Varma I am Santosh Varma, IT professional and working in this industry for the past 14 years. I am currently living in Bangalore, India, where I work as Test Manager in an IT company and also undertake some project management activities. What do you need to be agile on mainframes? Unit Tests on z/OS savvytest for System z enables you to continuously check the functionality of your software components on z/OS, and thus measure and document the substantial progress of your project after every iteration. www.savvytest.com The Magazine for Professional Testers Meet us at Swiss <strong>Testing</strong> Day, March 14th, Zurich Phone +49-7141-5071766 E-mail info@savvytest.com 39
Page 1: ISSN 1866-5705 www.testingexperienc
Page 4 and 5: Contents Editorial ................
Page 6: A Practitioner’s Guide to Integra
Page 9: 1. Set up requirements management.
Page 12 and 13: on testing has several disadvantage
Page 14 and 15: iography Bernhard Peischl is the co
Page 16 and 17: Lean approach through model-based t
Page 18 and 19: Knowledge Proprietary and managemen
Page 20 and 21: First model, then test! by Ben Viss
Page 22 and 23: And this last point was exactly the
Page 24 and 25: Watch out for Frenemies by Ian Moys
Page 26 and 27: of yours (for example, maybe you ha
Page 28 and 29: Conference (Day 1) May 16, 2012 Tim
Page 30 and 31: Model-Based Testing (MBT) provides
Page 32 and 33: © iStockphoto.com / davidnay © iS
Page 34 and 35: 4. Bertolino, A. Software testing r
Page 36 and 37: The challenge As test manager you
Page 38 and 39: are needed for business case valida
Page 42 and 43: © Sergejy Galushko - Fotolia.com C
Page 44 and 45: This article will be useful for tho
Page 46 and 47: i) Misunderstanding the business re
Page 48 and 49: Note: Memory Leak: A bug in a progr
Page 50 and 51: Incident (definition by IEEE): An i
Page 52 and 53: How do you collect the metrics to a
Page 54 and 55: Teams Defects per man day Team 1 1.
Page 56 and 57: It was evident that the amount of t
Page 58 and 59: Does Model-based Testing contribute
Page 60 and 61: More complex and inter-connected au
Page 62 and 63: Model-Based Testing - Practical app
Page 64 and 65: Start End Start Customer Order Fulf
Page 66 and 67: Hypothesis Based Testing - A person
Page 68 and 69: STEM Discipline Objective Used in H
Page 70 and 71: Examples SAAS / Bidding Software Ch
Page 72 and 73: Background Details In the wake of t
Page 74 and 75: For example, let’s assume that th
Page 76 and 77: Analyzing decision tables by Alon L
Page 78 and 79: Conditions: Values: Rule 1 Rule 2 R
Page 80 and 81: However, we can look at large sets
Page 82 and 83: 1. The loss of data quality The exi
Page 84 and 85: tions are: ▪ unique identifier is
Page 86 and 87: 4.3. Executing the data validation
Page 88 and 89: Beware!.... Model-based testing Wha
Page 90 and 91:
The success or failure of today’s
Page 92 and 93:
Finite State Machines in Model-Base
Page 94 and 95:
Masthead EDITOR Díaz & Hilterschei
Page 96:
Training with a View Dates * Course
show all

Model-Based Testing - Testing Experience

Create successful ePaper yourself

Delete template?

Save as template?