Business Systems Analyst & Designer


Jaroslaw Zelinski IT-Consulting

I have 30 years of exper­i­ence in the IT sys­tems mar­ket. I have been inde­pend­ently design­ing and super­vising imple­ment­a­tions for 20 years, the last 10 years also remotely. I have been involved in inform­a­tion and sys­tems mod­el­ing research for 15 years, and I am also an aca­dem­ic teach­er and have research experience.

Outsourced Ekspert of Business Analysis and System Design

(prices: ask about SLA plan)

Ongo­ing ana­lys­is of oper­a­tion­al doc­u­ments and the devel­op­ment and main­ten­ance of doc­u­ment­a­tion that includes busi­ness pro­cess mod­els and related inform­a­tion sys­tems archi­tec­ture. The goal is to col­lect and doc­u­ment know­ledge about the organ­iz­a­tion and man­age it in a way that allows it to be used imme­di­ately to make decisions about changes and present selec­ted inform­a­tion about the way things are done to outsiders.

  • col­lec­tion and ana­lys­is of source doc­u­ments, user stor­ies, etc,
  • Form­al­ized block dia­grams (BMM nota­tion) describ­ing busi­ness mod­els and com­pany strategies, and recom­mend­a­tions for effi­ciency improvements.
  • Form­al­ized block dia­grams (BPMN/SBVR nota­tions) describ­ing busi­ness pro­cesses, doc­u­ment flows and their struc­tures, and busi­ness rules and onto­lo­gies, recom­mend­a­tions for effi­ciency improvements.
  • Form­al­ized block dia­grams (UML nota­tion) and use-case spe­cific­a­tions, as graph­ic­al-descript­ive spe­cific­a­tions of soft­ware requirements.
  • Form­al­ized block dia­grams (UML nota­tion) describ­ing the HLD archi­tec­ture and logic of the sys­tem oper­a­tion and the LLD archi­tec­ture and busi­ness logic of each ded­ic­ated applic­a­tion ser­vice (use case) as spe­cific­a­tions for ded­ic­ated software.
  • Form­al­ized block dia­grams describ­ing the doc­u­ment and inform­a­tion struc­tures in the sys­tem and its flow (UML notation).
  • Stand­ard pro­fes­sion­al doc­u­ment­a­tion (A4, pdf) on-demand.

Classes and Workshops

NOTE: Pro­mo­tion­al prices to cel­eb­rate com­pany ini­ti­ation and train­ing in Aber­deen! All classes in prop­erty: Centrum Offices, 214 Uni­on St., AB10 1TL, Aber­deen. Ask about remote versions.

Daily timetable classes: 9:30 – 12:30, break, 13:30–16:30 (six hours a day). 

Business Process Management (£499)

Organ­iz­a­tions use Busi­ness Pro­cess Mod­el­ing in order to visu­ally doc­u­ment, under­stand, and improve their pro­cesses. BP Mod­el­ing visu­ally rep­res­ents all of the con­nect­ing activ­it­ies, events, and resources of the pro­cess of a product or ser­vice to make it more effi­cient. Soft­ware devel­op­ment is a risky field. Experts recom­mend devel­op­ing clear mod­els with under­stand­able nota­tion early on in pro­jects in order to val­id­ate the require­ments of the soft­ware. Busi­ness Pro­cess Mod­el­ing allows soft­ware engin­eers to nego­ti­ate with stake­hold­ers to determ­ine the sys­tem that needs to be built, based on what is optim­al for both groups.

Day 1

  • BPM intro­duc­tion,
  • busi­ness pro­cess mod­els: defin­i­tions, rules, 
  • CRUD and RACI matrix,
  • Busi­ness Architecture,
  • doc­u­ments as data car­ri­ers, doc­u­ments standardization, 

Day 2

  • BPMN found­a­tions,
  • Ana­lyt­ics mod­els in busi­ness analysis,
  • flow ele­ments
  • arti­facts,
  • pools and lines,
  • examples and their discussion.

Additions

Addi­tion­al prac­ti­cing work­shops are possible. 

(source: http://www.bptrendsassociates.com/)

Business Software Design (£499)

Pro­gram­ming is not solely about con­struct­ing soft­ware — pro­gram­ming is about design­ing software.

(Ozkaya, Ipek. ‘Build­ing Blocks of Soft­ware Design’. IEEE Soft­ware 37, no. 2 (March 2020): 3–5. https://doi.org/10.1109/MS.2019.2959049.)

Day 1

  • Sys­tem definition,
  • Object paradigm definitions,
  • “Sys­tem thinking”,
  • Busi­ness soft­ware archi­tec­ture and integration,

Day 2

  • What is it: MOF, MDA, UML,
  • basic con­cepts: class, clas­si­fi­er, value, pack­age, structure,
  • sys­tem design SPEM pro­cess: use case mod­el, use case scen­ario, use case realization,
  • UML dia­grams: class dia­gram, state machine dia­gram, inter­ac­tion dia­gram, activ­ity dia­gram, com­pon­ent diagram,

Additions

Addi­tion­al prac­ti­cing work­shops e.g.: busi­ness pro­cess map­ping and design, Use Case 2.0 style sys­tem design, doc­u­ment-ori­ented data mod­el­ing, microservices archi­tec­ture in prac­tice, sys­tem integ­ra­tion design, mechat­ron­ic sys­tem mod­el­ing with SysML, etc.

Groups

Groups, up to 6 people, can pay £1000 togeth­er for one daily class. 

Methodologies and tools


Object-Oriented Analysis and Design with Unified Modeling Language (OOAD with UML)

  • Object ori­ented paradigm: under­stand­ing and use 
  • MOF (Meta Object Facil­it­ies) as found­a­tion of UML nota­tion .
  • UML nota­tion: using for mod­el­ing object ori­ented sys­tems .
  • Mod­el-View-Con­trol­ler (MVC) pat­tern: what is it domain Mod­el in OOAD. 
  • OOAD: how do we use UML dia­grams and for what. Prac­tice. (Use Case dia­gram and use case scen­ario, sequence dia­gram, class dia­gram: sep­ar­ate archi­tec­ture, vocab­u­lary and data types, state machine dia­gram, activ­ity dia­gram, data types in UML/OOAD).
  • Doc­u­ment and mock-up mod­el­ing with UML com­pos­ite struc­ture dia­gram as a classes , NoSQL – doc­u­ment-ori­ented data­base ,
  • Mod­el Driv­en Architecture 
  • More about used meth­ods and tools: see on one of my papers.

Business Process Management and Business Modeling with BPMN and SBVR

  • Busi­ness Pro­cess Man­age­ment, defin­i­tions and scope .
  • BPMN nota­tion: using for busi­ness pro­cess doc­u­ment­a­tion, ana­lys­is and design, optim­iz­a­tion . Descript­ive and Ana­lyt­ic models. 
  • BPMN and oth­er aux­il­i­ary tools .
  • SBVR vocab­u­lary and rules as a busi­ness logic description 

Business analysis, requirements gathering – model-driven approach

  • Incom­plete­ness prob­lem in tex­tu­al require­ments spe­cific­a­tions .
  • Mod­el as a requirements 
  • Dis­cip­lined agile meth­ods , agile modeling 
  • Use Case 2.0
  • Mod­el Based Sys­tem Engin­eer­ing (MBSE) .

I offer high-qual­ity ser­vices in the field of busi­ness ana­lys­is, require­ments spe­cific­a­tion, and soft­ware archi­tec­ture design. All my works are based on Mod­el Driv­en Archi­tec­ture approach (MDA) . It means each ana­lys­is includes: the busi­ness ana­lys­is work stage (Com­pu­ta­tion Inde­pend­ent Mod­el design, CIM), require­ments spe­cific­a­tion stage (Use Case mod­el and scen­ario design, as a needed applic­a­tion ser­vices spe­cific­a­tion), and solu­tion design as a tech­nic­al descrip­tion of (Plat­form Inde­pend­ent Mod­el design, PIM) .

I use MBSE meth­ods (see INCOSE page). As an ana­lyst and design­er, I need a domain expert per­son to work (as an author­ized domain know­ledge provider). 

I use the latest proven meth­ods. As a research­er and aca­dem­ic lec­turer, I have the­or­et­ic­al know­ledge too and I know the latest soft­ware engin­eer­ing trends. Thru the last 30 years, I have had many suc­cesses in doing pro­jects for private and pub­lic companies.

CASE software

I’m an exper­i­enced user of one of the best CASE soft­ware (full range Visu­al-Paradigm CASE soft­ware since 2005), if you need any help on how to use CASE sys­tems, how to do mod­el­ing in UML, BPMN, SysML, and so on, ask me about the workshop. 


Keywords: Enter­prise Archi­tect, Busi­ness Ana­lyst, Design Author­ity, Solu­tion Design­er, Solu­tions Architect.

More

Bibliography

Ambler, S. W. (2004). The object primer. Agile Mod­el-Driv­en Devel­op­ment with UML 2.0 (Third Edi­tion). Cam­bridge Uni­ver­sity Press.
Ambler, S. W. (2002). Agile mod­el­ing. John Wiley & Sons.
Aßmann, U., Zschaler, S., & Wag­n­er, G. (2006). Onto­lo­gies, meta-mod­els, and the mod­el-driv­en paradigm. In Onto­lo­gies for soft­ware engin­eer­ing and soft­ware tech­no­logy (pp. 249–273). Springer.
Booch, G. (2007). Object-ori­ented ana­lys­is and design with applic­a­tions (G. Booch, Ed.; 3rd ed). Addison-Wesley.
Booch, G., Chris­ter­son, M., Fuchs, M., & Koistin­en, J. (1999). UML XML Map­ping Schema. 8.
BPMDS (Work­shop), Rein­hartz-Ber­ger, I., Zdravkovic, J., Gulden, J., Schmidt, R., EMMSAD (Work­shop), & CAiSE (Con­fer­ence). (2019). Enter­prise, Busi­ness-Pro­cess and Inform­a­tion Sys­tems Mod­el­ing: 20th Inter­na­tion­al Con­fer­ence, BPMDS 2019, 24th Inter­na­tion­al Con­fer­ence, EMMSAD 2019, Held at CAiSE 2019, Rome, Italy, June 3–4, 2019, Pro­ceed­ings (Vol. 352). Spring­er Inter­na­tion­al Pub­lish­ing. http://link.springer.com/10.1007/978–3‑030–20618‑5
Cabanil­las, C., Res­i­nas, M., & Ruiz-Cortés, A. (2012). Auto­mated Resource Assign­ment in BPMN Mod­els Using RACI Matrices. In R. Meers­man, H. Pan­etto, T. Dillon, S. Rinderle-Ma, P. Dadam, X. Zhou, S. Pear­son, A. Fer­scha, S. Ber­ga­mas­chi, & I. F. Cruz (Eds.), On the Move to Mean­ing­ful Inter­net Sys­tems: OTM 2012 (Vol. 7565, pp. 56–73). Spring­er Ber­lin Heidel­berg. https://doi.org/10.1007/978–3‑642–33606-5_5
Daoust, N. (2012). UML require­ments mod­el­ing for busi­ness ana­lysts (First edi­tion). Tech­nics Publications.
Den­nis, A., Wix­om, B. H., & Roth, R. M. (2012). Sys­tems ana­lys­is and design (5th ed). John Wiley.
Hart, L. E. (2015). Intro­duc­tion To Mod­el-Based Sys­tem Engin­eer­ing (MBSE) and SysML. Delaware Val­ley INCOSE Chapter Meet­ing, 43. https://www.incose.org/docs/default-source/delaware-valley/mbse-overview-incose-30-july-2015.pdf
Kurt Bittner. (2011). Use-Case 2.0: Scal­ing up, scal­ing out, scal­ing in for agile pro­jects. https://www.ivarjacobson.com/publications/white-papers/use-case-ebook
Miller, J., & Mukerji, J. (2003). MDA Guide Ver­sion 1.0.1. 62.
Object Man­age­ment Group. (2016, Octo­ber). MetaOb­ject Facil­ity (MOF). OMG.Org. https://www.omg.org/spec/MOF
Object Man­age­ment Group. (2014, June 18). Mod­el Driv­en Archi­tec­ture (MDA). OMG.Org. https://www.omg.org/mda/
Papamarkos, G., Zam­boulis, L., & Poulovassil­is, A. (2015). Xml Data­bases. School of Com­puter Sci­ence and Inform­a­tion Sys­tems, Birk­beck Col­lege, Uni­ver­sity of Lon­don. http://www.dcs.bbk.ac.uk/~sven/adm08/xmlDBs.pdf
Podeswa, H. (2010). UML for the IT busi­ness ana­lyst: a prac­tic­al guide to object-ori­ented require­ments gath­er­ing (2nd ed). Course Technology/Cengage Learning.
Šen­kýř, D., & Kroha, P. (2019). Prob­lem of Incom­plete­ness in Tex­tu­al Require­ments Spe­cific­a­tion: Pro­ceed­ings of the 14th Inter­na­tion­al Con­fer­ence on Soft­ware Tech­no­lo­gies, 323–330. https://doi.org/10.5220/0007978003230330
Šilin­gas, D., & But­ler­is, R. (2009). Towards imple­ment­ing a frame­work for mod­el­ing soft­ware require­ments in MagicDraw UML. Inform­a­tion Tech­no­logy and Con­trol, 38(2).
Sirichar­oen, W. V. (2007). Onto­lo­gies and object mod­els in object ori­ented soft­ware engin­eer­ing. IAENG Inter­na­tion­al Journ­al of Com­puter Sci­ence, 33(1), 19–24.
Zel­in­ski, J. (2020). Syn­thes­is of MOF, MDA, PIM, MVC, and BCE Nota­tions and Pat­terns. In Applic­a­tions and Approaches to Object-Ori­ented Soft­ware Design: Emer­ging Research and Oppor­tun­it­ies (pp. 78–89). IGI Glob­al. https://www.igi-global.com/book/applications-approaches-object-oriented-software/235699

"Programming is not solely about constructing software—programming is about designing software." (Ipek Ozkaya, Carnegie Mellon Software Engineering Institute, ipek.ozkaya@computer.org)