-
Notifications
You must be signed in to change notification settings - Fork 1
/
sepm_module.html
712 lines (339 loc) · 23.5 KB
/
sepm_module.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
<!DOCTYPE HTML>
<!--
Forty by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<head>
<title>Marianne Lyne Manaog</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="stylesheet" href="assets/css/main.css" />
<noscript><link rel="stylesheet" href="assets/css/noscript.css" /></noscript>
</head>
<body class="is-preload">
<!-- Wrapper -->
<div id="wrapper">
<!-- Header -->
<!-- Note: The "styleN" class below should match that of the banner element. -->
<header id="header" class="alt style2">
<a href="index.html" <span>Marianne Lyne Manaog</span></a>
<nav>
<a href="#menu">Menu</a>
</nav>
</header>
<!-- Menu -->
<nav id="menu">
<ul class="links">
<li><a href="index.html">Home</a></li>
<li><a href="oois_module.html">OOIS module</a></li>
<li><a href="oois_reflections.html">Reflections - OOIS</a></li>
<li><a href="ns_module.html">NS module</a></li>
<li><a href="ns_reflections.html">Reflections - NS</a></li>
<li><a href="ssdcs_module.html">SSDCS module</a></li>
<li><a href="ssdcs_reflections.html">Reflections - SSDCS</a></li>
<li><a href="sepm_module.html">SEPM module</a></li>
<li><a href="sepm_reflections.html">Reflections - SEPM</a></li>
<li><a href="rmpp_module.html">RMPP module</a></li>
<li><a href="rmpp_reflections.html">Reflections - RMPP</a></li>
</ul>
</nav>
<!-- Banner -->
<!-- Note: The "styleN" class below should match that of the header element. -->
<section id="banner" class="style2">
<div class="inner">
<span class="image">
<img src="images/pic07.jpg" alt="" />
</span>
<header class="major">
<h1>Software Engineering Project Management</h1>
</header>
<div class="content">
<p>Software Engineering and Project Management methodologies in the Software Development Life Cycle (SDLC), <br />
such as Behaviour Driven Development (BDD), Agile (Scrum and Kanban), and TOGAF.</p>
</div>
</div>
</section>
<!-- Main -->
<div id="main">
<!-- One -->
<section id="one">
<div class="inner">
<header class="major">
<h2>Lessons learnt and key outcomes</h2>
</header>
<p>Via the units mentioned below, I learnt to appreciate and apply the fundamentals of software engineering best practices and project management frameworks, critically assess their suitability throughout the SDLC and learn from case studies involving software engineering project-related failures to devise, manage, and deliver successful software engineering-related projects adopting robust and modern principles, best practices, and methodologies. These techniques involved appropriate definition of requirements as per the key user personas, tailored design to meet their prioritised needs and wants, robust design, software implementation and testing, gathering their early feedback, and enhancing the software throughout the SDLC, including via user acceptance testing (UAT). Furthermore, I learnt and applied various project management methodologies in traditional and modern SDLC models, such as TOGAF and Agile (both Scrum for delivery implementations and Kanban for fast-paced discovery-/hypothesis testing-related work), to build a working prototype of a remote-controlled race car-related game as a software application. In this team project, I learnt the importance of leveraging the team members' passion, skills, and expertise to design and deliver a software systems to meet key users' requirements whilst promoting diversity and inclusion in car racing, and complying with applicable data privacy regulations considering the storage and processing of required personal data, such as the European Union (EU)’s General Data Protection Regulations (GDPR).</p>
</div>
</section>
<!-- Two -->
<section id="two" class="spotlights">
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2023/02/15/06/08/success-7791029_1280.jpg" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 1: Introduction to Software Engineering Project Management</h3>
</header>
<p>Project management involves resource management, estimating the required work to deliver a software, and planning for its design, delivery, and support. Thus, it is crucial to have the required multi-disciplinary skillset and focus on execution by leveraging project management-related frameworks, such as Agile (Scrum, Kanban, or Scrumban), to support and accelerate modern software development projects. Such methodologies are more suitable than waterfall for large-scale client-focused software development and delivery, being centred on iteratively enhancing the product based on early feedback from end users. To understand and appreciate the importance of project management, case studies on software engineering-related project failures were explored. You can download my post as a part of a group discussion by clicking 'LEARN MORE' below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/collaborative_discussions/Collaborative_Discussion_1_Project_Failures_Study.docx?raw=true" target="_blank" rel="noopener noreferrer" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2022/11/17/22/02/multitasking-7598993_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 2: Study: Why Projects Fail and Gathering Requirements Exercise</h3>
</header>
<p>Gathering requirements as aligned as possible with the key user personas is key to ensure a software engineering-related project is set up for success. To this purpose, the Gherkin tool was introduced and further discussions were held on software engineering-related project failures introduced during the previous unit. You can download my responses to my peers by clicking ‘LEARN MORE’ below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/collaborative_discussions/Peer_responses_first_collaborative_discussion.docx?raw=true" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2017/11/09/08/43/business-tasks-2932687_1280.png" alt="" data-position="25% 25%" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 3: Estimating, Planning and Risk</h3>
</header>
<p>In this unit, I learnt the art and science of project management in software engineering in further depth, particularly on estimating the required work appropriately whilst considering risks and dependencies, and actions to mitigate them. In this week, I had the chance to ponder on the discussion with my peers during the previous two units and provided a summary post, which can be downloaded by clicking ‘LEARN MORE’ below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/collaborative_discussions/Summary_Post_Project_Failures_Study.docx?raw=true" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2022/12/01/11/47/risk-7628950_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 4: Risk Assessment and Estimating Tools</h3>
</header>
<p>This unit enabled me to learn tools to assess risks and estimate the work to be carried as a part of a software engineering-related project within the Agile framework, with focus on Scrum. This methodology is useful in large-scale software project delivery and informed my summary post on recommending mitigating actions to the risks identified, which led to software engineering-related project failures reviewed during case studies over the previous units. You can read my contribution by clicking ‘LEARN MORE’ below and please click on 'More pages' once landed on GitHub at the bottom of the page to read the section entitled 'Risks and Dependencies' wherein I leveraged the Risks, Assumptions, Issues, Dependencies (RAID) model to outline risks that were ranked based on their degree of severity, which stem from interdependent requirements that may impact delivery negatively.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/assignments/assignment_1_project_report/Project%20Plan%20Child%20Toy%20-%20SEPM_PCOM7E.pdf" target="_blank" rel="noopener noreferrer" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2016/08/27/12/06/website-1624028_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 5: User Experience</h3>
</header>
<p>This unit enabled me to learn and understand how important user experience is to ensure adoption of a system. In particular, I had the chance to ponder on the role and influence of the Project Manager in ensuring a smooth user experience from the first impression through to the support of users during the adoption of a system. In this unit, I contributed to a collaborative discussion with a post that you can download by clicking ‘LEARN MORE’ below, which focuses on further contextual elements and key users' expectations to account for to ensure a smooth user experience and drive adoption of a system.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/collaborative_discussions/Collaborative_discussion_2_initial_post.docx?raw=true" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2017/06/10/07/18/list-2389219_1280.png" alt="" data-position="25% 25%" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 6: pytest and Test-Driven Development</h3>
</header>
<p>During this unit, testing technologies available in Python, such as the library 'pytest', were explored to support test-driven development (TDD). Such testing tools are essential to drive the development and delivery of high-quality, functional codes that can ensure a correct and smooth user experience, thus eliciting positive emotional responses and the subsequent adoption by the end users. You can access my pytest exercise by clicking ‘LEARN MORE’ below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/tree/main/codio_activities/pytest_exercise" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2017/10/18/23/26/recursion-icon-2865934_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 7: Software Development Life Cycles</h3>
</header>
<p>In this unit, I had the chance to appreciate the role of the Project Manager throughout the SDLC and their influence to drive further user adoption by ensuring a smooth user experience, incorporating their feedback to enhance a system iteratively, in an agile manner. During this unit’s activity, I had the opportunity to ponder on the posts written by my colleagues and incorporated their complementary viewpoints into my summary post, which you can download by clicking ‘LEARN MORE’ below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/collaborative_discussions/Collaborative_discussion_2_summary_post.docx?raw=true" target="_blank" rel="noopener noreferrer" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2013/07/13/10/50/cabinet-157891_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 8: Python Data Structures</h3>
</header>
<p>This unit allowed me to study and practise on creating and handling various data structures in Python, such as dictionaries (key-value pairs), lists, and sets (considering their intersections, unions, etc.). Such structures enable to store data appropriately for various purposes depending on the application considered. Furthermore, I had the chance to investigate and test more complex data structures, such as two-dimensional vectors (the 'Vector2' class) in the Python library named 'pygame', which you can view at the unit tests-related file 'tests/rc_car/test_car.py' by clicking ‘LEARN MORE’ below. Such two-dimensional vectors were leveraged to represent and update the position of the race car in the game's environment considering both x and y coordinates (embedded in a two-dimensional vector).</p>
<ul class="actions">
<li><a href="https://github.com/SEPM-Nov-2022/sepm-rc-car/pull/54/files" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2022/06/23/11/55/quality-7279628_1280.png" alt="" data-position="25% 25%" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 9: Quality Management Strategy</h3>
</header>
<p>In this unit, I could learn and practise on how quality management strategies are crucial to a successful software and project delivery, including the appropriate use of linting tools or libraries in Python to ensure a high quality of the codes developed. In this instance, I had the chance to practise and appreciate how linting tools, such as the library 'pylint', can help to ensure a high code quality such that software can be consumed reliably by and is valuable to users. By clicking ‘LEARN MORE’ below, you can view my implementation of a GitHub Action to automate the linting check via pylint, as well as some improvements to the codes' style and docstrings to ensure the automated pylint-related code quality check on the GitHub Action I created passed (10/10 code quality).</p>
<ul class="actions">
<li><a href="https://github.com/SEPM-Nov-2022/sepm-rc-car/pull/29/files#diff-966efde8e4f3e50d6c03732c70ccfcca4a58830d4ef3b0ecffc1d61dd2386b10" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2016/04/01/09/52/boy-1299640_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 10: Software Quality Monitoring in Python</h3>
</header>
<p>Ensuring software quality involves iterative efforts and, thus, appropriate monitoring. To this purpose, various complementary libraries or tools in Python, such as the libraries pylint, pyflakes, pycodestyle, pydocstyle, were assessed and compared to support the development and delivery of high-quality code, thus accounting for different aspects, such as correct syntax and consistent style, as well as the presence of both classes' and methods' docstrings. You can access my hands-on assessment of various linting tools in Python by clicking ‘LEARN MORE’ below.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/tree/main/codio_activities/linters_for_python_code_quality" target="_blank" rel="noopener noreferrer" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2014/04/03/00/37/arrows-308888_1280.png" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 11: Software Engineering Project Management: Future Trends</h3>
</header>
<p>Trends and advances in software engineering and related project management were considered in both academic research and industry, such as Artificial Intelligence, the Internet of Things, and Quantum Cybersecurity. As a part of a team, I was one of the main contributors developing the presentation of a race car game we developed and tested in Python, along with its transcript. You can view my specific section on slide 8 regarding the testing of the application throughout the SDLC by clicking 'LEARN MORE' below. In fact, I not only contributed to add most of the unit tests to the codes developed, but also automated both unit test checks in a CI/CD pipeline via GitHub actions, which also runs automated checks for both security vulnerabilities and code quality/linting, thus not only verifying the correctness of the main applications’ functionalities, but also its security. Furthermore, I had created a conda virtual environment for us to work on the same environment in Python with the same dependencies, and created a Python package out of our application that can be installed via pip. I was also the main reviewer of my team members’ pull requests, aiming to achieve a high-quality software and presentation as per the assignment’s requirements.</p>
<ul class="actions">
<li><a href="https://github.com/marianne-manaog/sepm-module-activities/blob/main/assignments/assignment_2_project_presentation/SEPM%20Nov%202022%20Presentation%20Transcript.pdf" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2022/06/23/11/09/choose-7279556_1280.png" alt="" data-position="25% 25%" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Unit 12: Future Direction of Software Engineering Project Management</h3>
</header>
<p>In this unit, I had the chance to analyse the future direction of software engineering project management and ponder on our team's work and my contributions to it. In this software engineering project, I leveraged security by design as a key principle and automated security checks for any vulnerabilities in the open-source libraries used in Python via two libraries, 'safety' and 'bandit'. I automated these checks by including them in the CI/CD pipeline I built via GitHub Actions, which can be viewed by clicking 'LEARN MORE' below.</p>
<ul class="actions">
<li><a href="https://github.com/SEPM-Nov-2022/sepm-rc-car/pull/44/files" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
<section>
<a class="image">
<img src="https://cdn.pixabay.com/photo/2017/08/06/12/06/people-2591874_960_720.jpg" alt="" data-position="top center" />
</a>
<div class="content">
<div class="inner">
<header class="major">
<h3>Reflections on Software Engineering Project Management</h3>
</header>
<p>In this reflective piece, I summarised what I learnt on Software Engineering Project Management in this module, the work I carried out throughout it, and their impact on my personal and professional development. Click ‘LEARN MORE’ below to read it.</p>
<ul class="actions">
<li><a href="sepm_reflections.html" class="button">Learn more</a></li>
</ul>
</div>
</div>
</section>
</section>
</div>
<!-- Contact -->
<section id="contact">
<div class="inner">
<section>
<form method="post" action="#">
<div class="fields">
<div class="field half">
<label for="name">Name</label>
<input type="text" name="name" id="name" />
</div>
<div class="field half">
<label for="email">Email</label>
<input type="text" name="email" id="email" />
</div>
<div class="field">
<label for="message">Message</label>
<textarea name="message" id="message" rows="6"></textarea>
</div>
</div>
<ul class="actions">
<li><input type="submit" value="Send Message" class="primary" /></li>
<li><input type="reset" value="Clear" /></li>
</ul>
</form>
</section>
<section class="split">
<section>
<div class="contact-method">
<span class="icon solid alt fa-envelope"></span>
<h3>Email</h3>
<a href="#">marianne.manaog@ieee.org</a>
</div>
</section>
</section>
</div>
</section>
<!-- Footer -->
<footer id="footer">
<div class="inner">
<ul class="icons">
<li><a href="https://github.com/marianne-manaog" class="icon brands alt fa-github"><span class="label">GitHub</span></a></li>
<li><a href="https://www.linkedin.com/in/marianne-lyne-m/" class="icon brands alt fa-linkedin-in"><span class="label">LinkedIn</span></a></li>
</ul>
<ul class="copyright">
<li>© Marianne Lyne Manaog</li><li>Design: <a href="https://html5up.net">HTML5 UP</a></li>
</ul>
</div>
</footer>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/jquery.scrolly.min.js"></script>
<script src="assets/js/jquery.scrollex.min.js"></script>
<script src="assets/js/browser.min.js"></script>
<script src="assets/js/breakpoints.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
</body>
</html>