A new lecture course for technical students was started at the Grodno State University on the 15th of February. The course covers a wide range of questions in the field of project requirements analysis and business analyses in IT sphere.
One of the leading professionals of IntexSoft, Eugene Shashkov aspires to provide students with necessary knowledge about process modeling, project analyses, creation of important project documentation and project development cycle according to different development models (Waterfall, V-Model and Agile). In addition, future IT specialists have the opportunity to get useful information about budget planning and to look into the real software development process. Besides, Eugen Shashkov underlined, that it was very important to give students clear understanding about typical career stages at an IT company, for example, the way from junior developer position to Principal Software Architect job.
A command tells Selenium what to do. There are three 'types' of Selenium commands: Actions, Accessors and Assertions. Each command must contain command name, target and value:
Accessors examine the state of the application and store the results in variables, e.g. "storeText". They are also used to generate Assertions automatically.
Assertions are like Accessors, but they verify that the state of the application is as expected. All Selenium Assertions can be used in 3 modes: "assert", "verify", and "waitFor".
The main purpose of creating a software product is developing of such product, which helps users to carry out their daily tasks. At first, we need to define requirements such system should meet. However, if a user writes his list of demands, then we’ll get a list of functions.
According to this list, it will be hard to imagine what kind of application we need, what features have higher priority, and which user it is intended for.
To overcome this problem and to more accurately understand the process of system working, they started using description of system functionality through use cases (precedents) more often.
Use cases are descriptions of a sequence of actions that the system can perform in response to exposure of users or other software systems.