Infopaket

Production practice "Development of software information systems"

ННД.13

Обов’язкова дисципліна для ОП

Second

2023/2024

4 Semester

4

PLO01. Know and systemically apply in software design domain analysis and modeling methods, information requirements elicitation and input data collection methods. PLO02. Justify the choice of software requirements engineering, engineer, analyse, classify and prioritize requirements. PLO03. Know and apply fundamental concepts and methodologies of information processes modeling. PLO04. Estimate and choose methods and models for software systems development, deployment, maintenance and their management during all stages of software process. PLO05. Develop and estimate software design strategies; justify, analyze and estimate previously made design decision from the final software product quality perspective.

Distance form

Missed.

The purpose of the practice is to acquaint students with current practical approaches to testing and quality assurance of software. As a result of studying the discipline the student must: know the main stages of the software design process; know the purpose, capabilities and technologies of development and description of the developed software; know the principles of procedural and structural programming, basic types of language data, program management operators; be able to develop applications using the principles of procedural and structural programming; be able to test software on their own, both manually and with the help of modern tools for testing automation; substantiate their own view of the problem, communicate with colleagues on software development and testing, compile written reports; organize their independent work to achieve results; to be responsible for the work performed, to be responsible for its quality.

1. Beizer, Boris. Software Testing Techniques, 2nd edition, Boston, MA.: International Thomson Computer Press, 1990 (ISBN 1850328803). 2. Chrissis, M. B.; Konrad, M.; & Shrum, S. CMMI: Guidelines for Process Integration and Product Improvement. Boston, MA: Addison-Wesley, 2003 (ISBN 0321154967). 3. Cote, Marc-Alexis; Suryn, Witold; Martin, Robert A.; & Laporte, Claude Y. "Evolving a Corporate Software Quality Assessment Exercise: A Migration Path to ISO/IEC 9126.” Software Quality Engineering 6, 3 (2004). 4. Fenton, Norman E. & Pfleeger, Sharon L. Software Metrics: A Rigorous and Practical Approach, 2nd ed. Boston, MA: International Thomson Computer Press, 1996 (ISBN 1850322759). 5. Grady, Robert B. Practical Software Metrics for Project Management and Process Improvement. Englewood Cliffs, NJ: Prentice Hall, 1992 (ISBN 0137203845). 6. Halstead, Maurice. H. Elements of Software Science. New York, NY: Elsevier, 1977 (ISBN 0444002057).

Individual report on the internship: upon completion of the internship.

During the internship, the student must compile a written report, sign it by the company’s internship leader, put a stamp and together with a properly designed diary of the internship, characteristics-feedback from the company to hand over to the university’s internship leader. The report on practice is made after execution of sections of the program and processing of materials. Its registration ends at the enterprise by the end of the internship. It contains information about the type of practice, the topic of the individual task, the executor of the report and the head of the practice. The task for practice contains information about the name of the task (module), the term of the individual task, the input data for solving the tasks of the individual task, a list of graphic material, the signature of the head of the EIA and the student. The grade is defined as the sum of all points for all components provided by the discipline program.

Ukrainian