Telecommunication Software Development
Theoretical and practical knowledge about software engineering concepts and existing industrial best practices, software processes, methods and models for telecommunication software development. Ability to analyze software lifecycle from software process perspective. Ability to identify relationship between technology, project, team structures, development models, tools and development organization strategy. Understanding different roles of software lifecycle stakeholders. Research skills in analyzing business idea. Skills of collecting and analyzing software requirements and using tool for software requirements management.
- define concept of software product lifecycle
- identify software processes and software development models
- explain principles of software process tailoring
- explain business analysis and strategy definition principles
- identify critical points of analyzed process
- describe all aspects of software product vision
- apply techniques for software elicitation and analysis
- apply tool for software requirement management
Forms of Teaching
Teaching is organized in two cycles. First cycle includes 7 weeks of teaching and mid-term exam, and second cycle includes 6 weeks of teaching and final exam. Teaching is executed in 15 weeks with two hours of teaching per weekExams
Mid-term exam is in written form. Final exam and exam consist of written and oral parts.Laboratory Work
The exercises will be held in three cycles x 4 hours: (1) Elaboration and presentation of business idea (2) Specification and Requirements Management Tool (3) Implementation of the conceptual software solution in a prototyping toolConsultations
Course content is additionally explained to students during in individual consultations.Other
Guest lectures with the topic on best software practices.Acquisition of Skills
Writing software vision document for given software product case study, using introspection technique for requirements elicitation, working with software requirements management tool, defining software architecture, creating use case diagrams, business analysis.Other Forms of Group and Self Study
Independent research of rapid development methods and creating presentation on the subject.
|Type||Threshold||Percent of Grade||Threshold||Percent of Grade|
|Laboratory Exercises||50 %||15 %||50 %||15 %|
|Homeworks||50 %||10 %||50 %||10 %|
|Class participation||0 %||10 %||0 %||10 %|
|Mid Term Exam: Written||50 %||30 %||0 %|
|Final Exam: Written||50 %||25 %|
|Final Exam: Oral||10 %|
|Exam: Written||50 %||55 %|
|Exam: Oral||10 %|
Week by Week Schedule
- Introduction - domain description, history, definitions. Business and software processes.
- Software concept elaboration and business analysis - idea, presentation, business plan, financing
- Requirements engineering process. Techniques for software requirement elicitation, analysis and management
- Software product lifecycle and development models
- Agile development - assumptions and preconditions. XP, Scrum.
- Software usability and accessibility.
- Software maintenance process. Process and user documentation. Change and configuration management.
- Mid-term exam
- Architectures and software development technologies 1
- Architectures and software development technologies 2
- Future trends prediction and complex system evolution. Intellectual property and patents.
- Research and development in information and communication technology.
- Licensing in software domain.
- Invited lecture
- Final exam